Re: [HACKERS] Rule system goes weird with SELECT queries

2000-10-19 Thread Tom Lane
"Kevin O'Gorman" <[EMAIL PROTECTED]> writes: > When I actually *execute* the 'insert into dummy', I get the output of > only one select: the second one listed. Is there something about > executing a list I don't know about, or is this also old news?? If you're using psql then that doesn't surpri

Re: [HACKERS] Rule system goes weird with SELECT queries

2000-10-19 Thread Kevin O'Gorman
Thanks for the reply. I'll look into setting up CVS -- I've just been using the distributed 7.0.2 actually. Moreover, the situation is even a bit more confused for me. When I actually *execute* the 'insert into dummy', I get the output of only one select: the second one listed. Is there someth

Re: [HACKERS] Rule system goes weird with SELECT queries

2000-10-19 Thread Tom Lane
"Kevin O'Gorman" <[EMAIL PROTECTED]> writes: > If I define two rules for the same action, each with > a single select command, I wind up with two selects as > expected, but they are both cross-product selects on the > two tables. This is unexpected. Rangetable leakage, sounds like --- the two qu

[HACKERS] Rule system goes weird with SELECT queries

2000-10-19 Thread Kevin O'Gorman
I must admit I'm trying to (ab)use the rule system into being a stored-procedure system, so maybe I'm just getting what I deserve. However, the results I'm getting are just plain weird. If I define two rules for the same action, each with a single select command, I wind up with two selects as e