Back to Seed Clases

Gda

Classes

Interfaces

Structs

Unions

Enums

Enum Gda.ConnectionOptions

Import line:	Gda = imports.gi.Gda;
GIR File:	Gda-4.0.gir
C documentation:	GdaConnectionOptions
Enum :	ConnectionOptions
	Show / Hide Inherited methods, properties and signals

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 Additional information about the GDA_CONNECTION_OPTIONS_THREAD_SAFE and GDA_CONNECTION_OPTIONS_THREAD_ISOLATED flags: The GDA_CONNECTION_OPTIONS_THREAD_SAFE flag specifies that it has to be able to use the returned connection object from several threads at once (locking is ensured by the GdaConnection itself). Depending on the database provider's implementation and on the native libraries it uses, the "normal" connection object might not respect this requirement, and in this case a specific thread is started and used as the unique thread which will manipulate the actual connection, while a "wrapper connection" is actually returned and used by the caller (that wrapper connection passes method calls from the calling thread to the actual connection's specific thread, and gets the results back). The GDA_CONNECTION_OPTIONS_THREAD_ISOLATED forces using a specific thread and a "wrapper connection" even if the "normal" connection would itself be thread safe; this is usefull for example to be sure the asynchronous API can always be used (see gda_connection_async_statement_execute()). Having a specific thread and a "wrapper connection" definitely has an impact on the performances (because it involves messages passing between threads for every method call), so using the GDA_CONNECTION_OPTIONS_THREAD_SAFE or GDA_CONNECTION_OPTIONS_THREAD_ISOLATED flags should be carefully considered.

Values
Properties
	Number Gda.ConnectionOptions.NONE : 0
	Number Gda.ConnectionOptions.READ_ONLY : 1
	Number Gda.ConnectionOptions.SQL_IDENTIFIERS_CASE_SENSITIVE : 2
	Number Gda.ConnectionOptions.THREAD_ISOLATED : 8
	Number Gda.ConnectionOptions.THREAD_SAFE : 4

Properties
None

Public Methods
None

Events
None

Used by These Methods / Signals / Properties
Class / Namespace	Method / Signal / Properties
Gda.Connection Property	options : Gda.ConnectionOptions
Gda.Connection Method	Gda.Connection.open_from_dsn (String *dsn, String auth_string, ConnectionOptions options*) : Gda.Connection This function is the way of opening database connections with libgda, using a pre-defined data source (DSN), see gda_config_define_dsn() for more information about how to define a DSN.
Gda.Connection Method	Gda.Connection.open_from_string (String *provider_name, String cnc_string, String auth_string, ConnectionOptions options*) : Gda.Connection Opens a connection given a provider ID and a connection string.
Gda.Connection Method	get_options () : Gda.ConnectionOptions Gets the GdaConnectionOptions used to open this connection.