Postgres Pro
Downloads
Home   >   mailing lists

Thread: Error explaination?

Error explaination?

From
"Josh Berkus"
Date:
Folks,
I have a fuction that creates a record in a table called user_locks,
does a bunch of stuff, then deletes the record.  However, when I try to
run it, I get the following error:

ERROR:  triggered data change violation on relation "user_locks"
It appears that the function handler won't let me create, then delete
the same record.  What goes on?

-Josh Berkus


______AGLIO DATABASE SOLUTIONS___________________________                                      Josh Berkus Complete
informationtechnology      josh@agliodbs.com  and data management solutions       (415) 565-7293 for law firms, small
businesses       fax 621-2533   and non-profit organizations.      San Francisco

Re: Error explaination?

From
Jan Wieck
Date:
Josh Berkus wrote:
> Folks,
>
>    I have a fuction that creates a record in a table called user_locks,
> does a bunch of stuff, then deletes the record.  However, when I try to
> run it, I get the following error:
>
> ERROR:  triggered data change violation on relation "user_locks"
>
>    It appears that the function handler won't let me create, then delete
> the same record.  What goes on?
   You  have  a foreign key constraint or other triggers on that   "user_locks" table.
   This is a known misbehaviour (not to call it a bug)  that  we   keep since having deferrable referential integrity.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: Error explaination?

From
"Josh Berkus"
Date:
Jan,
Thanks for the quick response.

>     This is a known misbehaviour (not to call it a bug)  that  we
>     keep since having deferrable referential integrity.
Some sort of "catch 22" I take it?
Am I correct in understanding that my choices are to: a) do something
other than deleting the records, or b) drop the referential integrity
check on the table?
                    -Josh


______AGLIO DATABASE SOLUTIONS___________________________                                      Josh Berkus Complete
informationtechnology      josh@agliodbs.com  and data management solutions       (415) 565-7293 for law firms, small
businesses       fax 621-2533   and non-profit organizations.      San Francisco