Please enable JavaScript to view this site.

Discourse Forums

Discourse Data Model

Navigation: » No topics above this level «

Discourse SQL Driver Attributes

The SQL driver for Discourse has many attributes that can be finetuned to improve handling in scenarios with unreliable network connections to the API server of Discourse or high volumes of data. Also, many drivers have driver-specific attributes to finetune actual behaviour or handle data not matching specifications.

The Discourse driver attributes are assigned a default value which seldom requires change. However, changes can be applied when needed on four levels, which are reflected in the table below by separate checkmarks:

•Connection string: the connection string from the settings*.xml file and applied during log on.

•Set SQL statement: a set SQL-statement to be executed once connection has been established.

•Log on: value to be specified interactively by user during log on in a user interface.

itgen_doc_expl078_dot The reference manuals contain instructions how to relocate the settings*.xml files. Settings*.xml files are typically located in the </text><text styleclass="Code Example In Regel" translate="true">%USERPROFILE%\invantive</text><text styleclass="Normal" translate="true"> folder in most deployment scenarios. The reference manuals contain instructions how to relocate the settings*.xml files. Each data container of a database in the connection string can have a </text><text styleclass="Code Example In Regel" translate="true">connectionString</text><text styleclass="Normal" translate="true"> element specifying the name and values of attributes. Both name and value must be properly escaped according to XML-semantics. Actual application of the value is solely done during log on. A new connection must be established to change the value of a driver attribute using a connection string.

The set SQL statement can be executed after log on. The syntax is: </text><text styleclass="Code Example In Regel" translate="true">set NAME VALUE</text><text styleclass="Normal" translate="true">, or for a distributed database: </text><text styleclass="Code Example In Regel" translate="true">set NAME@ALIAS VALUE</text><text styleclass="Normal" translate="true">. In some scenarios you may need to enclose the driver attribute name in square brackets to escape it from parsing, for instance when a reserved SQL keyword is part of the name. The new value takes effect straight after execution of the set-statement. The set-statement can be executed as often as needed during a session.

Driver attributes that can be interactively set to a value are typically presented in the log on window. Depending on the platform and design decisions of the user interface designer, some or all of the available driver attributes can have been made available.

The Discourse driver can be configured using the following attributes:

itgen_doc_code

itgen_doc_description

itgen_doc_origin

itgen_doc_default_value

itgen_doc_set_connection_string

itgen_doc_set_set_sql

itgen_doc_set_drivers

itgen_doc_set_log_on

 

20-12-2022 08:27 Version 22.1.101-BETA+3681

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer