On Wed, 16 May 2001, Jonathan Ellis wrote:
> > > Would manually
> > > removing it from pg_trigger cause Bad Things to happen?
> >
> > Yes, and you'll need to double quote the trigger name.
> > try
> > drop trigger "RI_ConstraintTrigger_44349" on users;
>
> That worked. Why was that?
It's a mix
> > Would manually
> > removing it from pg_trigger cause Bad Things to happen?
>
> Yes, and you'll need to double quote the trigger name.
> try
> drop trigger "RI_ConstraintTrigger_44349" on users;
That worked. Why was that?
> How did you drop the table? Did you reload a dump file (like the on
On Wed, 16 May 2001, Jonathan Ellis wrote:
> This is in 7.1.1:
>
> I was playing around with a table called user_comments and then dropped it.
> One of its columns referenced the user_id column of another table, users.
> Now whenever I try to update users, I get results like this:
> bf2-new=# up
This is in 7.1.1:
I was playing around with a table called user_comments and then dropped it.
One of its columns referenced the user_id column of another table, users.
Now whenever I try to update users, I get results like this:
bf2-new=# update users set last_visit=sysdate() where user_id=4; ERR
