OOo's current philosophy regarding table privileges (i.e. the rights of the user
to do operations on tables such as INSERT, UPDATE, DELETE) is that the system
driver (i.e. the ODBC/JDBC driver provided by the database vendor) is asked for
these privileges, and that OOo's user interface disables any functionality which
the driver claims is not allowed.

There was a time where this approach seemed to work pretty well, but nowadays,
it's more and more common that database drivers to improperly implement the
getTablePrivileges, returning insufficient/incomplete/wrong information there.
Examples are MySQL (ODBC as well as JDBC), PostgreSQL, and Oracle.

We should have at least an option which allows to override this, and ignore the
privileges from the system driver. This option should be per-datasource (or
globally??), of boolean type, and, when set, cause the respective SDBC driver to
assume all privileges present. In such a case, OOo's UI would allow all
operations, but then present the possibly resulting errors to the user.

We should implement such a flag for at least the JDBC and the ODBC bridge.

FS->OJ: I suggest IgnoreSystemTablePrivileges, on a per-datasource basis. A user
interface for this is out-of-reach for 1.1, but we can do this later on, and for
the moment, handle this new setting like the ParameterNameSubstitution setting
(means it can be switched by using a Basic macro).