Stephan Szabo wrote:
>
> When you drop and recreate the table, you'll need to drop and recreate the
> rules that reference it as well. There's been little to no concensus as to
> what the correct behavior should be in such cases: delete the rules when
> a referenced table is removed, refuse to remove the table due to the
> references, try to reconnect by name (and somehow handle the possibility
> that the reference is no longer valid, like say the lack of a logid column
> in your case)...
>
>
Okay, thanks, dropping and recreating the rule worked.
After thinking a bit about this, it would seem that the 'problem' is
that I was *able* to drop a table that had rules referencing it. Would
it be possible to either not allow this, or to issue some type of
warning message? Otherwise, you go down the path of this (for me
anyway) subtle problem.
Also, who should I send documentation patches to about this? I couldn't
find any mention of this issue in the "create rule" documentation (or am
I looking in the wrong place?) or in "Chapter 17: The Postgres Rule
System". Hmmm, further perusal shows that Jan Weick is the author of
the Chapter 17 documentation, I guess I can send text to Jan.
--
-**-*-*---*-*---*-*---*-----*-*-----*---*-*---*-----*-----*-*-----*---
Jon Lapham
Extracta Moléculas Naturais, Rio de Janeiro, Brasil
email: [EMAIL PROTECTED] web: http://www.extracta.com.br/
***-*--*----*-------*------------*--------------------*---------------
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
