Query Lists

Query lists allow solving the following tasks:

Query list views must have the following fields:

TABLE_SCHEMA	TABLE_NAME	TABLE_TYPE	TABLE_CODE	INSERT_PROCEDURE	UPDATE_PROCEDURE	DELETE_PROCEDURE	PROCEDURE_TYPE

Views can have an optional first ID column.

Query list views are similar to the xls.objects table.

The key differences are:

Users must choose a query list in the SaveToDB/DBEdit Connection Wizard or via DBGate/ODataDB URL while the xls.objects configuration is loaded by default.
Query lists select objects available to connect while the xls.objects table configures objects only.
Query lists allow creating configurations on the fly, for example, depending on user permissions.
Objects defined in xls.objects can be used as handlers in the xls.handlers table.

You can create query list views from scrach or using the xls.queries view as a source.

The query list views have two logical parts.

The left part is used to specify configured objects.

TABLE_SCHEMA	TABLE_NAME	TABLE_TYPE	TABLE_CODE
<schema>	<table name>	TABLE
<schema>	<view name>	VIEW
<schema>	<procedure name>	PROCEDURE
<schema>	<new name>	CODE	<SQL>
<schema>	<new name>	HTTP	<HTTP Command>
<schema>	<new name>	TEXT	<Text file query>

Objects defined using SQL codes, HTTP commands, or text file queries have nearly the same features as native database objects.

See additional details:

The right part is used to configure saving changes and merging data.

Below are available options:

See additional notes: