> "Mathew Frank" <[EMAIL PROTECTED]> writes:
> > The documentation on this is very thin on the ground - I`ve just spend 4
Ho=
> > urs googling and the best I could find was one of the main developers
(Bruc=
> > e?? sorry - too long ago) replying to
I have had a lot of trouble getting a DELETE
trigger to do nothing (ie let the delete operation occur instead of cancelling
it, as required)
The documentation on this is very thin on the
ground - I`ve just spend 4 Hours googling and the best I could find was one of
the main developers (Bru
i have the following utility function, which I use to easily return the OID
of an the new row created by an INSERT query:
---
CREATE FUNCTION insert_record_return_oid(text) RETURNS int4 AS
' DECLARE
s_query ALIAS FOR $1;
oid int4;
BEGIN
EXECUTE s_query;
GET DIAGNOSTICS oid
> which appears correct (you misspelled the column name).
>
> 7.2 does foreign key validity checking in a funny order that causes it
> to produce the other error message first. While not incorrect, it's
> sure misleading :-(
Thanks a bunch.
I'm always a bit nervous about calling anything a bug.
Hello people,
I'm a newbie to this list (though I've been hanging around on the ODBC list
for some time and I've been working with pgSQL for about 8months) so go
easy? ;-)
I realise this error is to stop a bad foreign key reference being created.
However I have a table with a multi-column primary
