Automatic OIDs on each table row were removed from PostgreSQL a while
back (v7.3?), so it is time they got removed from Kannel's code. You
can still of course use OIDs if you create your tables with a syntax
something like:
CREATE TABLE (
....
) WITH OIDS;
On Jun 17, 2008, at 01:23, Hillel wrote:
Hi,
That is a great suggestion and should work, but it’s still a bug as
each database implementation should have the same Kannel
configuration. If you change databases you should not need to have
a different Kannel configuration per database.
Rgds
From: Andreas Fink [mailto:[EMAIL PROTECTED]
Sent: 16 June 2008 11:55 PM
To: Hillel
Cc: devel Devel
Subject: Re: Bug in Postgresql implementation
I guess oid is a database own id for identifying the row. So add a
field oid to your database and make it autofilled with a sequencial
id.
On 16.06.2008, at 22:55, Hillel wrote:
Hi,
We recently tried to use PostgreSQL rather than mysql and Kannel
can’t remove the DRL from the PostgreSQL database. When Kannel
tries to delete a dlr it has found, it throws an error and tries to
use the column called "oid":
2008-06-16 00:12:40 [10326] [7] DEBUG: removing DLR from database
2008-06-16 00:12:40 [10326] [7] DEBUG: sql: DELETE FROM dlr WHERE
oid = (SELECT oid FROM dlr WHERE smsc='smsc1' AND ts='334517' LIMIT
1);
2008-06-16 00:12:40 [10326] [7] ERROR: PGSQL: DELETE FROM dlr WHERE
oid = (SELECT oid FROM dlr WHERE smsc='smsc1' AND ts='334517' LIMIT
1);
2008-06-16 00:12:40 [10326] [7] ERROR: PGSQL: ERROR: column "oid"
does not exist
2008-06-16 00:12:40 [10326] [7] ERROR: PGSQL: DB update failed!
From mysql there is no problem:
2008-06-12 07:01:04 [3561] [12] DEBUG: removing DLR from database
2008-06-12 07:01:04 [3561] [12] DEBUG: sql: DELETE FROM dlr WHERE
smsc='smsc1' AND ts='288856' LIMIT 1;
Any suggestions for a patch?
Thanks
