• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
[SOLVED] RE: Entity Modeler - Strange Behaviour?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[SOLVED] RE: Entity Modeler - Strange Behaviour?


  • Subject: [SOLVED] RE: Entity Modeler - Strange Behaviour?
  • From: "Peter Thompson" <email@hidden>
  • Date: Fri, 14 Mar 2008 12:17:23 +1300
  • Thread-topic: [SOLVED] RE: Entity Modeler - Strange Behaviour?

Mike,
 
Yes your are correct.  From the MySQL manual:
A TIMESTAMP column is useful for recording the date and time of an INSERT or UPDATE operation. By default, the first TIMESTAMP column in a table is automatically set to the date and time of the most recent operation if you do not assign it a value yourself. You can also set any TIMESTAMP column to the current date and time by assigning it a NULL value. Variations on automatic initialization and update properties are described in Section 10.3.1.1, “TIMESTAMP Properties”.
Learning something new everyday!
 
Many thanks for your help!
 
Cheers,
Peter


From: webobjects-dev-bounces+peter.thompson=email@hidden [mailto:webobjects-dev-bounces+peter.thompson=email@hidden] On Behalf Of Mike Schrag
Sent: Friday, 14 March 2008 12:12 p.m.
To: AppleWO List
Subject: Re: Entity Modeler - Strange Behaviour?

Are you sure "timestamp" is the correct external type?  I seem to recall that timestamp on mysql actually is a last modified stamp?  hazy memory, though.

ms

On Mar 13, 2008, at 7:09 PM, Mike Schrag wrote:


Begin forwarded message:
From: "Peter Thompson" <email@hidden>
Date: March 13, 2008 6:49:07 PM EDT
To: "Mike Schrag" <email@hidden>
Subject: RE: Entity Modeler - Strange Behaviour?

WO 5.3, MySQL, WoLips 2.0.0.4118.
 
Thanks,
Peter

From: webobjects-dev-bounces+peter.thompson=email@hidden [mailto:webobjects-dev-bounces+peter.thompson=email@hidden] On Behalf Of Mike Schrag
Sent: Friday, 14 March 2008 11:40 a.m.
To: AppleWO List
Subject: Re: Entity Modeler - Strange Behaviour?
Importance: High

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?
Entity Modeler doesn't generate SQL, it uses EOF.  What version of WO, what database, what plugin?

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

 _______________________________________________
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

References: 
 >Fwd: Entity Modeler - Strange Behaviour? (From: Mike Schrag <email@hidden>)
 >Re: Entity Modeler - Strange Behaviour? (From: Mike Schrag <email@hidden>)

  • Prev by Date: Re: Entity Modeler - Strange Behaviour?
  • Next by Date: [SOLVED] RE: Entity Modeler - Strange Behaviour?
  • Previous by thread: [SOLVED] RE: Entity Modeler - Strange Behaviour?
  • Next by thread: FInally
  • Index(es):
    • Date
    • Thread