Query Lists

Query Lists

Query lists allow solving the following tasks:

  • Defining objects available to connect
  • Defining objects based on SQL code
  • Defining objects based on HTTP requests
  • Defining objects based on text file queries
  • Configuring saving changes
  • Configuring merging data

Query list views must have the following fields:


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.

<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:

<schema>.<table name><schema>.<table name><schema>.<table name>
<schema>.<view name><schema>.<view name><schema>.<view name>
<schema>.<procedure name><schema>.<procedure name><schema>.<procedure name>
<schema>.<procedure name>
<schema>.<table name>
<schema>.<view name>
<schema>.<procedure name>
<HTTP Command><HTTP Command><HTTP Command>

See additional notes: