On Tue, 02 Dec 2008 09:13:00 +0100 Christoph Zwerschke <[EMAIL PROTECTED]> wrote: > Sorry, somehow I totally missed your posting. It's unusual that you have > insert but not select privilege, but you're right it can happen and > selecting will abort a transaction in this case. I agree that it's > probably best to add a flag for suppressing the select since I see no > easy way to check the select privilege in advance (since it could be > obtained/inherited in some obscure indirect ways). By default, the > select should be made (backward compatibility, and usually it works).
OK, I will do this at least. > Using "returning *" will of course not solve this problem since it will > also fail if there is no select privilege, but it is more efficient, and > it will also work when the table has no oids. But unfortunately, the > returnig clause exists only in Postgres >= 8.2. Maybe this and other > method should get another parameter "use_oids" with a default value that > can be set or changed for the complete DB() instance. This issue could be put off until later since it is an optimization. We can introduce that in a minor release. -- D'Arcy J.M. Cain PyGreSQL Development Group http://www.PyGreSQL.org _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
