Re: MS SQL and NSTimestamp.DistantFuture
Re: MS SQL and NSTimestamp.DistantFuture
- Subject: Re: MS SQL and NSTimestamp.DistantFuture
- From: Alan Ward <email@hidden>
- Date: Fri, 18 Apr 2008 10:39:43 -0600
I believe the problem is that Microsoft has never really considered
what the distantFuture may have in store for them.
One of these days they'll have a sudden awakening....
:-)
Alan
On Apr 18, 2008, at 2:22 AM, David Avendasora wrote:
I ended up implementing my own "DistantFuture" method in my Utility
class. Not the greatest, but it works like a charm.
I can't believe that Chuck hasn't come up with a fix for this MS
SQL "shortcoming". He's fixed so many others.
Slacker. He probably can't.
Dave
On Apr 17, 2008, at 10:37 PM, Lachlan Deck wrote:
On 18/04/2008, at 1:45 AM, David Avendasora wrote:
Apparently MS SQL Server does not like the value
NSTimestamp.DistantFuture tries to send to the database.
After capturing the exact SQL and trying it out using Aqua Data
Studio, I get the following error: "Syntax error converting
datetime from character string."
The value it is trying to use is: '292278994-08-17 02:12:55'
MS SQL doesn't like anything more than a 4-digit year.
Don't tell me we learnt nothing from the y2k bug... and it's now a
y10k bug ;-)
I suppose I could just not use NSTimestamp.DistantFuture, and
pass a date like '9999-12-31 23:59:59' or something. Any better
suggestions for a work-around?
Perhaps you could override your setters (via velocity) to call
some transformFunction that'll round down a few years for mysql?
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden