From: Dan Langille <dan@la...> - 2003-12-11 04:35:22
Just a quick note before I finish for the day. I've been able to get
the Bacula daemons running with PostgreSQL. I can label volumes, list
them, and run a job. Problems exist with referential integrity.
10-Dec-2003 23:30 polo-dir: BackupCatalog.2003-12-10_23.29.56 Warning:
Error updating job record. sql_update.c:148 update UPDATE Job SET
JobStatus='f', EndTime='2003-12-10 23:30:00', ClientId=0, JobBytes=0,
JobFiles=0, JobErrors=0, VolSessionId=0, VolSessionTime=0, PoolId=0,
FileSetId=0, JobTDate=1071117000 WHERE JobId=12 failed:
ERROR: $1 referential integrity violation - key referenced from job not
found in pool
In this case, the code is trying to set several fields to zero. This
violates referential integrity (there is no Pool with id = 0). I suspect
this may be as simple as not detecting a NULL value and translating it to
'NULL' instead of zero.
I *hope* it doesn't mean that I have to change the SQL.