Hi,
1. Initially we thought updates were not working.
However, we found out that updates to tables without
any foreign key constraints were working fine.
2. We created another dB and tables with foreign key
constraints. Once again, we found that updates to
tables with foreign key constraints were failing.
3. We had to take a quick decision. So, we just
reloaded 'postgres' and tried our luck. Guess what, it
worked!
Again we really don't know what is the cause.
Thanks Mr. Stephan Szabo
R. Subramaniam
--- Stephan Szabo <sszabo@megazone23.bigpanda.com>
wrote:
> On Mon, 6 Aug 2001, Subra Radhakrishnan wrote:
>
> > Hi All,
> >
> > This is what we did before we got the error:
> >
> > 1. Took a backup of existing dB (hospdb) using
> pg_dump
> > (full backup including schema and data)
> >
> > 2. Modified the schema to change the field size
> from
> > 200 to 600 (varchar data type)
> >
> > 3. Dropped the dB (hospdb)
> >
> > 4. Recreated the dB (hospdb)
> >
> > 5. Used psql to reload the schema and data
> >
> > 6. Now when I am using the dB and trying to update
> a
> > table, I get the following error message 'Wrong #
> of
> > arguments in call to RI_Fkey_key equals _upd()'
>
> What do the schema and create constraint trigger
> statements look like from the dump, and what is in
> pg_trigger?
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the
> unregister command
> (send "unregister YourEmailAddressHere" to
majordomo@postgresql.org)
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/