[BUG] ?
От | Geoff Ellis |
---|---|
Тема | [BUG] ? |
Дата | |
Msg-id | FDCF842C8B1DD311833C0090277C04B518C37D@augusta.planmatics.co.uk обсуждение исходный текст |
Список | pgadmin-support |
I was having a lot of trouble the other day and thanks to Tom Lane for his help in getting me up and running. I did find however that pgAdminII 1.4.12 did not drop triggers properly. I've enclosed a file which contains the db schema. Although, I couldn't get it to install the plpgsql language and create the database in pgAdminII so I had to create those on the command line. geoff@emsdev:~$ createdb test geoff@emsdev:~$ createlang plpgsql test bug === In pgAdmin, if you drop the function first, and refresh the schema, it shows that the trigger no longer exists on the table blah. However, you would still see the trigger using the psql interface and will have to drop it here otherwise you get cache lookup failed errors and can't install the trigger again as it already exists. If you drop the trigger first, this works fine. So I guess I'm saying you need to drop the trigger explicitly rather than doing it via dropping the function. Is this a feature or a bug? ;o) Sorry if this has been made aware... kind regards Geoff Ellis Metalogic PLC Burnsall Road Coventry UK. +44(0)2476678484
Вложения
В списке pgadmin-support по дате отправления: