Re: _exceptionWithDatabaseContextInformationAdded when trying to update SQL Server
Re: _exceptionWithDatabaseContextInformationAdded when trying to update SQL Server
- Subject: Re: _exceptionWithDatabaseContextInformationAdded when trying to update SQL Server
- From: Art Isbell <email@hidden>
- Date: Thu, 9 Sep 2004 09:24:48 -1000
On Sep 9, 2004, at 8:35 AM, Bill Reynolds wrote:
I know it's painful to look at - but in the statement below is there
anything painfully obvious that would cause the
"_exceptionWithDatabaseContextInformationAdded"?
In your eomodel, try unsetting lastoutlooksyncdatetime as used for
locking. Timestamps can be troublesome in some databases because of a
possible difference in precision between the DB data and an
NSTimestamp.
It's nice to be able to use a "lastUpdate" timestamp as the only
attribute used for locking because the "where" clause would contain
only the primary key and the lastUpdate timestamp. This can be a bit
faster for the DB to resolve. One way to avoid the precision problem
would be to store a timestamp with a precision of only 1 second which
is good enough in many situations.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.