Re: [SQLObject] Preparing for 0.4

[Ian B. <ia...@co...>]

Yes, I believe Bud pointed this out to me.

It's annoying, because TIMESTAMP in MySQL is funny, but Postgres'
TIMESTAMP is like MySQL's DATETIME.  On a related note, this kind of
makes me want to stick with StringCol (vs. TextCol)...

On Wed, 2003-04-23 at 07:58, David M. Cook wrote:
> Ah, so it does do something for a lot of people (e.g. RH 8 has PG 7.2 AFAIK),
> and it looks like it does the right thing in that case:
> 
> class DateTimeCol(Col):
> 
>     # 3-03 @@: provide constraints; right now we let the database
>     # do any parsing and checking.  And DATE and TIME?
> 
>     def _mysqlType(self):
>         return 'DATETIME'
> 
>     def _postgresType(self):
>         return 'TIMESTAMP'
> 	
> Dave
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss