Claudio,

> Ans what do you expect? That IBO guesses that the user has no privileges?
> :-)

maybe he expects to get an error message when the user tries to update,
not before. This way, he can deploy a single application and rely on
GRANT/REVOKE only to customize the access.

> IBO prepares the statement in advance, for efficiency.

If the statements are prepared every time they are needed, this would
surely be inefficient. A better solution would maybe be to prepare each
statement the first time it is needed; this would solve the problem and
also help reduce resource usage, I think. Dunno if it is easily doable,
though.

> I don't know if you plan to query system tables to see if some user is
> allowed to modify data. How did you expected this to happen? Black magic?

In the current situation, you are *forced* to query the system tables if
you want to deploy the same application to different categories of
users; I wouldn't do it; your solution will certainly work but it's
cumbersome and leads to multiplication by 4 of the number of data access
components needed in the application.

At the very least, an event that signals a prepare error, whose handler
gets passed the kind of statement (edit, insert, update...) could help.
I'm curious to know what Jason thinks about this one.
Regards
--
____
_/\/ando