Re: Re: [PEPr] Proposal for Database::DB_Table
| From: | Paul M Jones | Date: | Wed, 07 Jan 2004 15:53:42 +0000 |
| Subject: | Re: Re: [PEPr] Proposal for Database::DB_Table | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24853@lists.php.net to get a copy of this message | ||
On Jan 7, 2004, at 9:46 AM, Daniel Convissor wrote:
On Wed, Jan 07, 2004 at 11:32:55PM +0800, Alan Knowles wrote:I don't understand... DB_Table defines a timestamp as a 4-byte integer, thus a Unix timestamp. This is portable across all RDBMSs. When using DB_Table, you know (regardless of the RDBMS) exactly how your timestamp is going to be stored and retrieved. Perhaps you were offering advice on DB_DataObject in the DB_Table thread? BTW, great resource. :-) -- Paul M. Jones pmjones@ciaweb.net Savant: the simple alternative to Smarty. http://phpsavant.com/- think about timestamp (which is not very portable),Perhaps this will help: http://www.analysisandsolutions.com/code/dates.htm It's an overview of several DBMS's and how to get them to handle the standard ISO date and timestamp formats for input and output.