Core database connections
Databases are mandatory in the implementation of some features of TORO Integrate. These required databases are what we call core databases. By default, TORO Integrate creates these databases for you albeit in the form of embedded HSQL databases which, in most cases, is not ideal for production environments and warrants migration.
TORO Integrate's core databases are:
This database is mainly used for building reports.
Used for storing all Flux-related data.
Other pre-configured database connections
Any other database connection that is pre-configured but not a core database connection are most likely created
and used by the
examples package. It does not affect the functionality of TORO Integrate in
any way and can be safely deleted if desired.
Like regular databases, TORO Integrate communicates with core databases via database connections. We call database connections of core databases, core database connections. Core database connections are also pre-configured in TORO Integrate.
As seen in the user interface
In Coder, your instance's existing database connections can be shown by expanding the Databases node in the Coder Navigator view. In the Server Admin UI, they are listed in the Databases page.
Like any other database connection, the core database connections' statuses can be changed. However, keep in mind that there are a few key differences.
Although core database connections can be stopped so that they could be re-configured or migrated, deleting a core database connection would only reset its configuration to its default counterpart (as in TORO Integrate will revert to using embedded databases). Meanwhile, disabling core database connections is not possible because TORO Integrate requires these databases to run.
In addition to this, any changes made to core database connections would require you to restart TORO Integrate.
Stop core database connections with caution
Stopping any of the core database connections would cause some functions to not work properly in TORO Integrate.