This document applies to SQLEditor 2 (versions 2.7.x and 2.8.x)
Due to a bug, this release of SQLEditor always uses the "Generic" dialect when exporting via the clipboard (copy/paste) instead of the correct document dialect
This has been fixed in the latest beta: SQLEditor 2.9.2b1 (58M zip file)
or use the in-app auto-updater by checking "Check for beta versions"
Due to two missing files in the build, the "Release Notes" and "Readme" options in the help menu don't work
(Fixed in a later release)
If exporting to SQLite, with an auto increment primary key, the type must be integer or the export may fail
There are a number of SQL keywords which cannot be used as identifiers in SQL files when importing into SQLEditor.
Later versions of SQLEditor have an improved parser which should reduce the number of reserved words.
If you have a table and reorder the fields in SQLEditor, this reordering may not be exported to the database.
Work is continuing on this issue.
Use uppercase, Oracle JDBC drivers seem to expect schema names to be in uppercase
Please upgrade to the latest available JDBC driver, which should fix the problem (or use the built in native driver instead)
SQLEditor will only recognize drivers that are included on its internal list. If the driver isn't on this list then it will not be recognized automatically and you will need to add it by hand.
See the SQLEditor database drivers page for details of supported drivers
If you install drivers while it is running it may not recognise them immediately. Try restarting SQLEditor to see if this makes any difference.
Drag using the drag handle on the left of the field. If no handle is visible try clicking on the field first
Files without extension or with the extensions sql,text or txt can be imported
MySQL versions 5.2 and later want to use keyword "ENGINE" instead of "TYPE" for specifying table engine types (INNODB, MyISAM, etc)
Earlier versions of SQLEditor used "TYPE", new releases now correctly use "ENGINE"
To contact us with a support issue please email: