Reverse engineering Oracle DB in EOModeler
Reverse engineering Oracle DB in EOModeler
- Subject: Reverse engineering Oracle DB in EOModeler
- From: Carter Wojcik <email@hidden>
- Date: Wed, 26 Apr 2006 10:29:35 -0700 (PDT)
Hi All -
I am currently working on a project that has a legacy
Oracle database. It uses the column type Date instead
of Timestamp. Are there any benefits of using
Timestamp over Date?
As an example, we have an auditing attribute named
dateAdded of type Date. When creating a model from
the existing database, the following attribute
characteristics are populated:
Name: dateAdded
Value Type: D
External Type: DATE
ValueClass (Java): NSTimestamp
Are these the correct (preferred) settings or should
they be set to something else? If we were to use
Timestamp for dateAdded in the database, would Value
Type = T and External Type = Timestamp? Can you use a
Value Type = T in the above example?
Thanks for the help.
Carter
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
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