On Wed, 2007-01-17 at 10:01 -0500, John Siracusa wrote: > I'm forwarding this private email thread to the list with the > permission of the (now anonymized) sender because it's about an > unexpected situation that many RDBO users may face. Yes, it revolves > around yet another fun feature of MySQL/DBD::mysql. How did you > guess? :)
Hmm. It sounds like the problem was that he marked some columns NOT NULL but wanted them to accept NULL. When MySQL is not in strict mode, that causes the columns to use generic defaults when passed NULL, hence the column_info data from DBD::mysql saying that this column defaults to empty string. The best thing to do is to run MySQL 5 or later with strict mode enabled, so that trying to put NULL into a NOT NULL column will be a fatal error (like it is in most databases). That makes it obvious where the problem is. - Perrin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rose-db-object mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rose-db-object
