|
|
Posted by Roy Harvey on 06/27/07 02:11
On Wed, 27 Jun 2007 02:04:39 -0000, "jshunter@waikato.ac.nz"
<jshunter@waikato.ac.nz> wrote:
>On Jun 27, 1:56 pm, Roy Harvey <roy_har...@snet.net> wrote:
>> How about just hardcoding what is in the documentation? DATETIME, for
>> example says "Date and time data from January 1, 1753 through December
>> 31, 9999, to an accuracy of one three-hundredth of a second
>> (equivalent to 3.33 milliseconds or 0.00333 seconds)." Which after
>> consulting the accompanying chart comes to 9999-12-31 23:59:59.997.
>>
>> Roy Harvey
>> Beacon Falls, CT
>
>I've had to do just that, but it would be nice if I could have the
>view do the job via a function. For example, if the underlying table
>changed from a smalldatetime to a datetime, then all views which use
>it would automatically return the correct maximum value
>
>--John Hunter
One alternative is to write your own function that encapsulates the
hardcode. Pass the table and column names, query the system tables
for the type and related information such as max length of a varchar,
and then return it. Clumsy, no doubt.
Or reconsider the design decision of using maximum values in place of
NULLs.
Roy Harvey
Beacon Falls, CT
Navigation:
[Reply to this message]
|