this flags specifies that if a #GdaMetaStore has been associated to the connection, then it is kept up to date with the evolutions in the database's structure. Be aware however that there are some drawbacks explained below.
no specific aspect
this flag specifies that the connection to open should be in a read-only mode (this policy is not correctly enforced at the moment)
this flag specifies that SQL identifiers submitted as input to Libgda have to keep their case sensitivity.
Specifies some aspects of a connection when opening it.
Additional information about the GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE flag:
For example without this flag, if the table
name specified in a #GdaServerOperation to create a table is
MyTable , then usually the database will create a table named
mytable , whereas with this flag, the table will be created
as MyTable (note that in the end the database may still decide
to name the table mytable or differently if it can't do
otherwise). Libgda will not apply this rule when parsing SQL code, the SQL code being parsed
has to be conform to the database it will be used with
Note about the
Every time a DDL statement is successfully executed, the associated meta data, if
defined, will be updated, which has a impact on performances If a transaction is started and some DDL statements are executed and the transaction
is not rolled back or committed, then the meta data may end up being wrong
GDA_CONNECTION_OPTIONS_AUTO_META_DATAflag: