NAME

sqlayindummy - a dummy SQL database engine driver for sqlay.

SYNOPSIS

libsqlayindummy.so

[sqlaytool] [options] dummy:[datasource]

DESCRIPTION

sqlayindummy is a dummy SQL database engine driver for sqlay. It simulates DML read-write and DDL, returning always success and random data or metadata.

It can be used as benchmarking or debugging tool for sqlay front-ends.

INVOCATION

The driver is loaded by giving as argument to the sqlaytool front-end executable a dummy: URL.

Alternatively, the dummy proto name can be replaced by the following alias: demo.

OPTIONS

This driver accepts options in the datasource URL. Please, also refer to the sqlayin(1) man page for options common to all drivers.

• Datasource:
  • The user, password, host, port options of the URL are ignored but the database and table names can be choosen in the followings based on compilation defaults for sizes, usually set around 20 tables and 60 rows:
    • empty No table at all.
    • tiny One tenth of compilation default.
    • small 0.4 * compilation default.
    • test Compilation defaults, also default if no database / table specified in the URL.
    • medium 5 * compilation default for number of tables, 10 * for number of rows.
    • normal 10 * compilation default for number of tables, 100 * for number of rows.
    • big 100 * compilation default for number of tables, 1000 * for number of rows.
    • huge 300 * compilation default for number of tables, 10,000 * for number of rows.

FEATURES

Here are features not or partially supported by this driver. Please, also refer to the sqlayin(1) man page for features supported or not by all drivers.

The driver does not simulate indexes, nor views, and input filters are ignored.

NOTES

Eventhough given values are not particularily above what one can encounter in real life RDBMS servers, this driver may crash whatever connects to it, as this is also one of the natural purposes of a benchmarking tool.

Pls understand that this is an alpha release and none of the executables is securized against buffer overflows, and so on. It is also not thread safe.

BUGS

See the NOTE above for important security warnings.

AUTHOR

E. Lurquin <sqlay@hitud.net>

SEE ALSO

sqlayin(1), sqlay(1), sqlsc(1), sqlds(1)