Initialization and configuration

Libgda initialization — Library initialization
Configuration — Access/Management of libgda configuration
Configuring libgda with environment variables

Configuration examples are given in this introduction section

Configuring libgda with environment variables

Some functional aspects of libgda can be configured using environment variables which are listed here:

  • GDA_CONNECTION_EVENTS_SHOW: if set, then lists the type of events which must be displayed on STDOUT (event types are NOTICE, COMMAND, WARNING, ERROR, the variable can contain a list of types separated by colons, commas or spaces)

  • GDA_CONNECTION_COMMANDS_SHOW: if set, then all the commands issued to a server will be displayed on STDOUT

  • GDA_DSN_LIST_IN_MEMORY: if set, then the list of defined data sources (DSN) will remain in memory (will not be written to disk) and will be lost when the application terminates.

  • GDA_PROVIDERS_ROOT_DIR: if set, must point to the directory where the providers files are (providers files are shared libraries)

  • LIBGDA_NO_THREADS: if set, then multi threading will be disabled (note that libgda is not thread safe, but usually internally uses threads when possible to perform actions in a non blocking way)

  • GDA_DATA_MODEL_DUMP_TITLE: if set, then gda_data_model_dump() will also output the name of the data model as its first line

  • GDA_DATA_MODEL_DUMP_ROW_NUMBERS: if set, then gda_data_model_dump() will prepend a column containing row numbers

  • GDA_DATA_MODEL_NULL_AS_EMPTY: if set, then gda_data_model_dump() will show an empty ("") string for NULL values, instead of the "NULL" string

  • GDA_DATA_MODEL_DUMP_ATTRIBUTES: if set, then gda_data_model_dump() will also include a description of the data model's attributes