> Hi,
>
> I don't know if it has anything to do with your problem, I just wanted to
> comment on the use of a timestamp column in a primary key...
>
> * David Bordas
> > +--------------+----------------------+------+-----+---------+----
> > ------------+
> > > > | Field | Type | Null | Key | Default | Extra
|
> > >
> > +--------------+----------------------+------+-----+---------+----
> > ------------+
> > > > | Pseudo | char(16) | | PRI | | |
> > > > | Date | timestamp(14) | YES | PRI | NULL | |
> > > > | Numero | smallint(5) unsigned | | PRI | NULL
> > |auto_increment |
> > > > | Type_message | enum('0','1') | | | 0 | |
> > >
> > +--------------+----------------------+------+-----+---------+----
> > ---------- --+
>
> The timestamp column will automatically be updated when any other field in
> the row is updated. This kind of "magic" is normally not wanted for
primary
> keys... :)
>
> <URL: http://www.mysql.com/doc/en/DATETIME.html >
>
I know that :)
But timestamp is quite great because it only uses 4 Bytes /row where
DateTime will use 8 Bytes / row.
And i'm only doing select / insert / delete so, timestamp is good for me.
David
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
