thanks for responding. Meanwhile I found out that ist was my own fault. A newly
installed insert trigger fired unexpectedly and caused the error. Now I'm
redesigning my functions to make them smaller so that errors can be found
easier. Sometimes I wish there was something like a debugger for
You can give EnterpriseDB PL Debugger a try, details for its usage can be
found at -- http://www.enterprisedb.com/documentation/debugger.html
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 1/14/07, Marcel Gsteiger [EMAIL PROTECTED] wrote:
thanks for responding. Meanwhile I
Marcel Gsteiger [EMAIL PROTECTED] writes:
Sometimes I wish there was something like a debugger for PL/PGSQL with
breakpoints, single step, variable watching...
Take a look at http://pgfoundry.org/projects/edb-debugger/
... it's beta but without users it won't get better.
The front page says
Marcel Gsteiger [EMAIL PROTECTED] writes:
Sometimes I wish there was something like a debugger for PL/PGSQL with
breakpoints, single step, variable watching...
Take a look at http://pgfoundry.org/projects/edb-debugger/
... it's beta but without users it won't get better.
The front page
Hi all
I have a PL/PGSQL conversion procedure that reads a source table and then
inserts tuples into several related tables. Recently I upgraded from 8.1 to
8.2.0, then to 8.2.1.
With 8.1 everything worked fine.
Now since I upgraded to 8.2 I have problems inserting data into tables that
have
Marcel Gsteiger [EMAIL PROTECTED] writes:
Now since I upgraded to 8.2 I have problems inserting data into tables that
have unique indexes. Ugly enough, I get the message 'duplicate key violates
unique constraint' when inserting the very first record into a table. This
happens everytime when
