Entity Modeler - Strange Behaviour?
Entity Modeler - Strange Behaviour?
- Subject: Entity Modeler - Strange Behaviour?
- From: "Peter Thompson" <email@hidden>
- Date: Fri, 14 Mar 2008 11:35:11 +1300
- Importance: high
- Priority: Urgent
- Thread-topic: Entity Modeler - Strange Behaviour?
Can the following
behaviour be explained please.
We have an attribute
defined in our model as:
Name -
endDate
Column -
END_DATE
External Type -
timestamp
Allows Null -
unchecked
Data Type -
Timestamp - NS Timestamp T
When I generate SQL
this attribute gets the following SQL generated:
`END_DATE`
timestamp NOT NULL default CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP,
While I can
understand the "default CURRENT_TIMESTAMP" why does it add the "on update
CURRENT_TIMESTAMP"? Can this behaviour be switched
off?
Thanks,
Peter
Peter
Thompson
Senior
Developer/Architect
Run The
Red
www.runthered.com
===================================
E: email@hidden
M: + 64 21 241
3266 / + 64 27 441 3255
DDI:
+ 64 4 801 2806
P:
+64 4 384 6880 F: +64 4 384
6875
Skype:
peterwgtnnz
PO Box
11-703,
Level 2 Tadix House,
1 Blair
Street,
Te Aro, Wellington
6011, New
Zealand
===================================
_______________________________________________
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