| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | cheng shan <postgresql_general(at)yahoo(dot)com(dot)cn> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Triggers don't activate when dropping table |
| Date: | 2004-12-07 12:22:40 |
| Message-ID: | 20041207041425.R82778@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 7 Dec 2004, cheng shan wrote:
>In the first version, the function destroy_object_type( ) just drop the
>table only. But when I find the triggers havn't
>been actived yet, I add the delete setense. This time it becomes even
>worse, the system throws error message.ERROR: could
>not open relation with OID 1390714.
>To avoid the fatal error, I have no choice but to rollback the function
>to the original version.
>I have written a simplified test cast to verify the system, but it
>performs as I expected and it's wrong.
Once I remove the bare text from the test case, my 8.0b3 system seems to
run the whole thing pasted in with no errors. What version are you trying
it against?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2004-12-07 12:26:37 | Re: Index scan vs. Seq scan on timestamps |
| Previous Message | Oleg Bartunov | 2004-12-07 11:20:07 | Re: Index on geometry and timestamp |