Current Limitations

This document lists various things that SQLEditor cannot currently do.

It is hoped to improve SQLEditor to add some of these features in future.

• Data vs Structure
• Triggers
• Table, partition and storage options
• Postgres Style Object Inheritance
• Functions and Procedures

Data vs Structure

SQLEditor works only with the structure of the database, it cannot edit the data stored within that structure.

See also: SQLEditor: Data vs Structure

Triggers

It is not currently possible to create Triggers

There is support for check constraints

Table, partition and storage options

There only limited support for viewing or editing table and storage options

SQLEditor supports more commonly used options, for example in MySQL, ENGINE is supported, but INSERT_METHOD is not (yet).

MySQL Supported Table Properties

Property	Supported
ENGINE
AUTO_INCREMENT (setting next increment value)
AVG_ROW_LENGTH
CHARACTER SET
CHECKSUM
COLLATE
COMMENT
CONNECTION
DATA DIRECTORY
DELAY_KEY_WRITE
INDEX DIRECTORY
INSERT_METHOD
KEY_BLOCK_SIZE
MAX_ROWS
MIN_ROWS
PACK_KEYS
PASSWORD
ROW_FORMAT
TABLESPACE
UNION

See MySQL Reference Manual: Create Table Syntax for more details on these properties.

We're planning on adding more support for these options in future versions.

Postgres Style Object Inheritance

SQLEditor does not support Postgres Object Inheritance.

For example, in Postgres you can have a table Animals and another table Elephants, the latter of which includes all of the columns in Animals but also adds TrunkLength as a column.

It's really clever, but not as yet supported in SQLEditor.

Functions and Procedures

You cannot currently define functions, macros or procedures for a database in SQLEditor