I get a small error during installation with the 1.1 beta7 when building the Postressql db. The error is:
ERROR: relation "escalations_log" does not exist
ERROR: relation "escalations_log" does not exist
I looked at the schema.sql file, and I think it comes from the following code block:
--------
CREATE TABLE escalation_log (
escalationlogid serial,
triggerid int4 DEFAULT '0' NOT NULL,
alarmid int4 DEFAULT '0' NOT NULL,
escalationid int4 DEFAULT '0' NOT NULL,
actiontype int4 DEFAULT '0' NOT NULL,
level int4 DEFAULT '0' NOT NULL,
adminlevel int4 DEFAULT '0' NOT NULL,
nextcheck int4 DEFAULT '0' NOT NULL,
status int4 DEFAULT '0' NOT NULL,
PRIMARY KEY (escalationlogid)
);
CREATE INDEX escalations_log_alarmid_escalationid on escalations_log (alarmid,escalationid);
CREATE INDEX escalations_log_triggerid on escalations_log (triggerid);
---------
I believe the issue is the table is called "escalation_log" but the index is being created on escalations_log. No big thing, but if this is just not me messing up, it might be worth loooking at.
There may also be an issue with escalations_log_triggerid already being a key named used elsewhere in the schema. Anyway, this I think would just be a performance tweak, not any kind of serious bug, if it is a bug.
On make, though, there is more nasty looking error:
db.c:234:2: #error SUPPORT OF POSTGRESQL NOT IMPLEMENTED YET
db.c: In function `DBaffected_rows':
Not sure what this means, other than perhaps this beta is not such a good idea to use with Postgres just now!
- Michael
ERROR: relation "escalations_log" does not exist
ERROR: relation "escalations_log" does not exist
I looked at the schema.sql file, and I think it comes from the following code block:
--------
CREATE TABLE escalation_log (
escalationlogid serial,
triggerid int4 DEFAULT '0' NOT NULL,
alarmid int4 DEFAULT '0' NOT NULL,
escalationid int4 DEFAULT '0' NOT NULL,
actiontype int4 DEFAULT '0' NOT NULL,
level int4 DEFAULT '0' NOT NULL,
adminlevel int4 DEFAULT '0' NOT NULL,
nextcheck int4 DEFAULT '0' NOT NULL,
status int4 DEFAULT '0' NOT NULL,
PRIMARY KEY (escalationlogid)
);
CREATE INDEX escalations_log_alarmid_escalationid on escalations_log (alarmid,escalationid);
CREATE INDEX escalations_log_triggerid on escalations_log (triggerid);
---------
I believe the issue is the table is called "escalation_log" but the index is being created on escalations_log. No big thing, but if this is just not me messing up, it might be worth loooking at.
There may also be an issue with escalations_log_triggerid already being a key named used elsewhere in the schema. Anyway, this I think would just be a performance tweak, not any kind of serious bug, if it is a bug.
On make, though, there is more nasty looking error:
db.c:234:2: #error SUPPORT OF POSTGRESQL NOT IMPLEMENTED YET
db.c: In function `DBaffected_rows':
Not sure what this means, other than perhaps this beta is not such a good idea to use with Postgres just now!
- Michael