Re^3: datetimestamp faster/golf/prettier

I have a few questions:

Which version of MySQL? The handling of TIMESTAMP changes in v4.1.0 and 4.1.2
What error are you seeing?
Can you show me the structure of the table and the code used to insert the value?

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

Comment on Re^3: datetimestamp faster/golf/prettier

Replies are listed 'Best First'.
Re^4: datetimestamp faster/golf/prettier by Jaap (Curate) on Jul 20, 2004 at 15:11 UTC
I'm very sorry. It is Class:DBI that gave me the error: `Can't create Doc::Node object with null primary key columns () at ./db +itest.pl line 38` [download]	[reply] [d/l]
Re^5: datetimestamp faster/golf/prettier by Joost (Canon) on Jul 20, 2004 at 15:16 UTC
Hmmmm Class::DBI allows "automatic" primary keys, but that seems to be only for AUTO_INCREMENT (not TIMESTAMP). You might want to suggest adding this behaviour at the cdbi mailinglist TIMESTAMP might not be unique, by the way, so using it as the primary key is not a very good idea IMHO. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]