>>>>> On Wed, 4 Jan 2006 17:27:30 +0100, Kern Sibbald <[EMAIL PROTECTED]> said:
Kern> On Wednesday 28 December 2005 21:57, Brian Keifer wrote: >> Quoting Martin Simmons <[EMAIL PROTECTED]>: >> > I think the setting of "strict mode" in the MySQL config is a possible >> > reason for this error. >> >> It sure is - good catch. =) Is it possible to run Bacula with this >> restriction >> in place? Kern> Sorry, no. The SQL standard is that table and column names are case Kern> independent, so I programmed it with consistent upper/lower case names. To Kern> change it would require changing a lot of code and making it a lot less Kern> readable. I don't think it is a case problem. Rather, it is caused by the REFERENCES and NOT NULL options such as this one: CREATE TABLE Job ( ... ClientId INTEGER NOT NULL REFERENCES Client, ... } When the job record is first inserted, the ClientId is unspecified, which leads to a consistency error when MySQL is running in strict mode. FWIW, the PostgreSQL tables are created without some of the NOT NULL options. __Martin ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
