Home → Using LincDoc 3.1+ → Configuring Storage Repositories → Specifying SQL Repository Connection Settings

12.6. Specifying SQL Repository Connection Settings

Once you create a SQL (Database-type) repository, there are several parameters to configure.

  1. Access the Configure dialog box as described in Creating a Repository.
  2. From the Database drop-down list, select the pre-defined database that you want to use as a repository. This list of available databases is determined using the databases option.
  3. From the Schema drop-down list, specify the desired schema to be used. All LincDoc database objects (tables, indexes, sequences, etc.) will be written to this schema.

    Note: When using the default LincDoc (PostgreSQL) database for your repository, the schema naming convention uses the current client id.

  4. (optional) Click the versioned check box to enable any object written to the repository to have its full version history available from the Browse dialog box.

    If versioning is enabled, the complete version history is kept for each file and LincDoc document. The version history can be viewed using the history button, and old versions can be promoted to be the current version. If versioning is disabled, a new version number is still created on each update, but old versions are immediately purged.

  5. (optional) In the Prefix text box, specify a text string that will be prepended to the beginning of the name of any object created within the selected database schema. This feature may be useful when using very large databases connected to multiple applications, allowing you to keep tables better organized (for example, using ld_ as the prefix for all LincDoc generated tables).

    Note: When using the default repository, this option is not as useful since only LincDoc uses the underlying database. By default, the default repository uses default_ for the prefix, and the resources repository uses resources_.

  6. (optional) In the Suffix text box, specify a text string that will be appended to the end of the name of any object created within the selected database schema. This setting is very similar in functionality and usage to the Prefix setting above. Typically, it is not used.
  7. (optional) Review the database commands that will be executed against the database to create the underlying objects that make up the repository by clicking the show system table DDL button. 
  8. Click test to verify your database connection.
  9. Click save.
  10. Proceed to Configuring a SQL Repository.

For Database-type repositories, table names are based on your eForm or Document Package name, the selected schema, and any prefix or suffix you specify using the following naming convention:

schema_name.table-name (with the table name including a prefix and suffix, if specified)

For example, if your eForm is named time_report, your schema is client_id, and you specified a prefix of ld_, then your table names would be the following:

This page was: Helpful | Not Helpful
← 27.3. Creating an Email Template