The Databases for Wolframe are configured in the Database
section of the configuration.
This section explains how to configure a Postgres database.
In order to use a Postgres database in Wolframe you have to configure the loading of the module mod_db_postgresql in the LoadModules section of your configuration. The addressed Postgres database server must be running and the database and the user configured must have been created before.
The configuration settings for PostgreSQL are splitted in two parts: The database configuration settings and the SSL configuration settings. The following three tables show the PostgreSQL database configuration settings, the PostgreSQL SSL configuration settings and the table with configurable SSL modes:
Table 3.10. PostgreSQL database configuration settings
Name | Parameter | Description |
---|---|---|
Identifier | identifier | Database identifier used to reference this database. |
Host | host name or IP address | Address of the PostgreSQL database server. Uses the unix domain socket if not defined. |
Port | number | Port of the PostgreSQL database server. The default is 5432. |
Database | identifier | Name of the database to connect to |
User | identifier | User to connect to the database with |
Password | string | Password to connect to the database with |
ConnectionTimeout | number | Connection timeout in seconds. The default if not specified is 30 seconds. A value of '0' disables the connection timeout. |
Connections | number | Maximum number of simoultaneus database connections (size of connection pool). Default if not specified is 4 connections. |
AcquireTimeout | number | Maximum time allowed to acquire a database connection in seconds |
StatementTimeout | number | The maximum allowed time to execute a statement in milliseconds. |
Table 3.11. SSL configuration settings
Name | Parameter | Description |
---|---|---|
SslMode | identifier | How a SSL TCP/IP connection should be negotiated with the server. Possible values and their explanation can be found in the SSL Mode table below. |
SslCert | filename | The file name of the client SSL certificate in case of an SSL connection to the database. |
SslKey | filename | The file with the secret key used for the client certificate in case of an SSL connection to the database. |
SslRootCert | filename | The File name of the root SSL CA certificate in case of an SSL connection to the database. |
SslCRL | filename | The File name of the SSL certificate revocation list (CRL) in case of an SSL connection to the database. |
Table 3.12. SSL modes
Name | Description |
---|---|
disable | Only try a non-SSL connection |
allow | First try a non-SSL connection. If that fails, try an SSL connection |
prefer | First try an SSL connection. If that fails, try a non-SSL connection. This is the default. |
require | Only try an SSL connection. If a root CA file is present, verify the certificate. |
verify-ca | Only try an SSL connection, and verify that the server. The certificate is issued by a trusted CA. |
verify-full | Only try an SSL connection, verify that the server certificate is issued by a trusted CA and that the server hostname matches that in the certificate. |
This section explains how to configure a Sqlite database.
In order to use an Sqlite3 database in Wolframe you have to configure the loading of the module mod_db_sqlite3 in the LoadModules section of your configuration. The database file configured must have been created before.
The following table shows the configuration settings for a Sqlite3 database in Wolframe.
Table 3.13. Sqlite3 database configuration settings
Name | Parameter | Description |
---|---|---|
Identifier | identifier | Database identifier used to reference this database. |
File | filepath | Store the SQLite database into the file specified as argument. This parameter is required and the file must have been created before. |
Connections | number | Number of simultaneous connections to the database. Specifies the size of the pool of connections used for database transactions. The default number of connections is 4 if not configured. |
ForeignKeys | yes or no | Setting foreignKeys to yes
enables referential integrity in the database. This is
actually the same as executing 'PRAGMA foreign_keys=true'.
The default is yes . |
Profiling | yes or no | Shows the SQL commands being executed and their
execution time in milliseconds. Default is no . |
Extension | filename | Loads the SQLite3 extension module specified as argument. This is useful to load native code into SQLite3 imlementing for instance new database functions. Have a look at the SQLite3 'Run-Time Loadable Extensions' section at http://www.sqlite.org/loadext.html. |
This section explains how to configure an Oracle database.
In order to use an Oracle database in Wolframe you have to configure the loading of the module mod_db_oracle in the LoadModules section of your configuration. The addressed Oracle database server must be running and the database and the user configured must have been created before.
The following table shows the Oracle database configuration settings:
Table 3.14. Oracle database configuration settings
Name | Parameter | Description |
---|---|---|
Identifier | identifier | Database identifier used to reference this database. |
Host | identifier or string | Address of the Oracle database server |
Port | number | Port of the Oracle database server, the default is 1521 if not specified |
Database | identifier | Name of the database to connect to, this is the Oracle SID. |
User | identifier | User to connect to the database with |
Password | string | Password to connect to the database with |
Connections | number | Maximum number of simultaneous database connections (size of connection pool) |
AcquireTimeout | number | Maximum time allowed to acquire a database connection in seconds |
Copyright © 2014 - Project Wolframe - All Rights Reserved