jwieck@debis.com (Jan Wieck) writes:
> I've seen the queryLimit by SET variable stuff and that
> really can break rewrite rules, triggers or functions. This
> is because the query limit will be inherited by any query
> (inserts, updates, deletes too) done by them.
> [ example snipped ]
> This is a feature where users can get around rules that
> ensure data integrity.
Ouch. I think this point is a *fatal* objection to implementing
query limit as a SET variable. That might be a quick-and-dirty way
of getting some functionality going, but we can't let it loose on the
world like that.
regards, tom lane
