RE: [PEAR-DEV] Modification in LiveUser SQL for Perm and Auth

Mysql uses the ISO format for time when you use datetime. This is the reason that MDB uses datetime instead of timestamp as liveuser used to. So if we use something else than datetime we loose MDB schema compatibility. We might decide that keeping MDB schema compatibility is too much of a hassle. That would be unfortunate, but these issues highlight the very reason that MDB was written: PEAR DB does not handle datatype abstraction and therefore you will probably never be able to write a performant sql schema that will work in all RDBMS's that PEAR DB supports. Regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de > -----Original Message----- > From: Bertrand Mansion [mailto:bmansion@mamasam.com] > Sent: Thursday, October 10, 2002 3:23 PM > To: Markus Wolff; Lukas Smith; 'PHP PEAR Developer'; Pierre-Alain Joye > Subject: Re: [PEAR-DEV] Modification in LiveUser SQL for Perm and Auth > > Hi again, > > I forgot to mention one more point about date/time fields. > I have noticed that all database support int() fields while they don't > support datetime fields the same way. For instance, in MySQL, you will use > DATE_FORMAT() while in Oracle, you use TO_CHAR() in your queries. > > Then, I suggest we use regular unix timestamps as they are very well > handled > by PHP and its date() function. The drawback is that, as raw data, they > are > not very much readable except if you naturally know how many seconds have > spent since 1 january 1970 :) > > Any opinions ? > > Bertrand Mansion > Mamasam > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php