current_delete AS
ON DELETE TO current
DO INSERT INTO former (number)
SELECT number FROM current
WHERE number = OLD.number
EXCEPT
SELECT number FROM trash;
--
Brandon Craig Rhodes http://www.rhodesmill.org/brandon
Georgia Tech
-l' which makes me wonder if I have done something horribly
wrong. Does anyone else see this?
--
Brandon Craig Rhodes http://www.rhodesmill.org/brandon
Georgia Tech[EMAIL PROTECTED]
---(end of broadcast
Tom Lane [EMAIL PROTECTED] writes:
[I do not see that error] here. Try a full recompile. (Unless you
configure with --enable-depend, a make distclean is a smart move
during *any* update from CVS.)
An initdb followed by rebuilding my tables fixed the problem.
--
Brandon Craig Rhodes
!
test-broken.sql
Description: Binary data
test-working.sql
Description: Binary data
--
Brandon Craig Rhodes http://www.rhodesmill.org/brandon
Georgia Tech[EMAIL PROTECTED]
---(end of broadcast
Tom Lane [EMAIL PROTECTED] writes:
Brandon Craig Rhodes [EMAIL PROTECTED] writes:
The `working' test case omits the
AND (account, policy) NOT IN
(SELECT account, policy FROM policy_accounts_active)
condition from the end of executor_active, which magically makes
combining into a
trunk, start branching out again to form roots - because the resulting
rows will not only be, say, inserted into a table, but might be shared
between several rules that will then have their own operations to
perform upon the result.
And yes, I am volunteering. :-)
--
Brandon Craig
