Thanks Chuck. WebObjects and Wonder behave correctly.
DOH! It was all me. We are using an Oracle database and the column type
is a DATE. Well Oracle DATE's have no millies and the rawRows returns
the correct value. In addition to that, when I came to my log statement
the dateModified had already been modified by a new NSTimestamp() which
of course has millis which don't get saved to the database. DOH!
Michael.
On 3/16/12 5:25 PM, Chuck Hill wrote:
Which method in which class are you using? Are you using the Wonder one that
takes a list of attributes? If not, it may be incorrectly inferring the type.
Chuck
On 2012-03-16, at 4:54 PM, Michael Hast wrote:
Hello:
I am experiencing an interesting issue. I have an EO that has a dateModified
attribute. I am fetching that EO and print out the dateModified (see below).
Everything is fine. Now I am doing a rawRowsForSQL fetch for that same
attribute and am getting back an NSTimestamp which appears to be the same, but
the milli seconds are 000. Why does the rawRowsForSQL query 0 out the milli
seconds?
sqlString: select DATE_MODIFIED from IDEA where IDEA_ID = 15347
NSTimestamp
rawRows value : 2012-03-16 22:35:03 Etc/GMT
EO value : 2012-03-16 22:35:03 Etc/GMT
NSTimestamp.getTime()
rawRows value : 1331937303000
EO value : 1331937303211
Michael.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
