Re: MySQL <> EOModeler timestamp question

Hi James,

I checked some old model files and found that i had used datetime  
instead of timestamp, and the problem never turned up.
Is there a disadvantage to using datetime as opposed to timestamp? I  
don't know.

http://dev.mysql.com/doc/mysql/en/datetime.html

from the first paragraph of the manual it appears that using datetime  
may be easier on the nerves:
The TIMESTAMP column type has varying properties, depending on the  
MySQL version and the SQL mode the server is running in. These  
properties are described later in this section.

On that note, does anyone know if it's possible to stream blobs to  
MySQL yet, or does it still hog the memory?

regards

Cornelius

On Jun 23, 2005, at 11:03 PM, james o wrote:

>
> trying to utilize MySQL for the first time and i have a question  
> with TimeStamps.  it looks like the current timestamp syntax for  
> MySQL is 0000-00-00 00:00:00.  i was getting an error in the  
> EOModeller asking for a timestamp with a GMT offset *i think*.   
> this error disappeared after i changed the adaptor to include:  
> zeroDateTimeBehavior=convertToNull
>
> adaptor: jdbc:mysql://64.80.202.72/icfdis? 
> zeroDateTimeBehavior=convertToNull&capitalizeTypenames=true
>
> after changing the adaptor i could browse the data in EOModeller  
> but the timestamp column was null.  i'm wondering if i adjust the  
> EOModel to accept this syntax or does MySQL need to be adjusted?
>
> WO Vers: 5.2.4
> DATABASE: MySQL 4.1.7
> JDBC connector: mysql-connector-java-3.1.9-bin.jar
>
> thanks,
> ./james
>
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>
>