Hi *,
I don't know if this is really a bug but surely is something that is
giving a lot of problems to psycopg (pyhton/postgresql adapter). psycopg
1.1.11+ checks for libpq version at runtime and, if available uses the
new protocol api (mainly to extract non-localized error codes after
errors). no
Dear Tom,
On Fri, 2004-04-30 at 19:48, Tom Lane wrote:
> Arturs Zoldners <[EMAIL PROTECTED]> writes:
> > -- The following rule prevents user x to update public_data:
> > CREATE RULE log_public AS ON UPDATE TO private_data WHERE (new.a <>
> > old.a) DO INSERT INTO private_log (old_val, new_val) VA
Arturs Zoldners <[EMAIL PROTECTED]> writes:
> I found another bug, which sounds very like the first one:
Hm, looks like no one ever experimented with permissions checking for
subqueries in a rule WHERE clause before. Fixed - thanks for the report!
regards, tom lane
-
Fabien COELHO <[EMAIL PROTECTED]> writes:
> For the TODO, I would suggest something general:
> - fix grant/revoke wrt SQL standard, validate errors, warnings and successes.
I have a patch-in-progress that addresses these issues. I didn't get it
quite finished before leaving for vacation, but hope
Bruce Momjian <[EMAIL PROTECTED]> writes:
> We have already fixed this in CVS and the fix will be in 7.5:
I don't think that the previous changes address what the complainant
seems to really want, viz not even *try* to exceed RLIMIT_NOFILE.
However the patch certainly must be rejected since (a) i
