This is a list of known bugs and some workarounds
- As described on the start page, you have to start sqlcockpit from the root
of the installation path, where the file sqlcockpit.pl resides. This is a
problem especially for Unix and Linux users. A solution would be to write
a small shell script (here a very
which cd's to sqlcockpit's root dir, then runs sqlcockpit. Install this script
in a path where your shell is looking for binaries (e.g. /usr/local/bin or
- Perhaps the most problematic thing about sqlcockpit is the bad documentation.
Even if there is a help system, the contents is partly in german, partly in
english and not up to date at all!
- The Edit and Statistic menues and there respective subitems
doesn't work correctly. This is due to the fact, that early versions of sqlcockpit
had it's output in text fields instead of a spreadsheet. Workaround: Simply
do not use them by the time. The only thing which goes well is 'Edit' =>'Add
- Options: In the subitem colcors you can configure a lot of
colors, but not all of these colors are used anymore. Not a severe bug, but
maybe for people who prefer playing with fonts and colors ...
- The font editor is not that nice as the Tk::Font selector. This is the reason
why only a few fonts are available, but they should be anough anyway. I wrote
this before Tk::Font was on the net ...
- A somewhat problematic(and missing) feature is the handling of long / blob
data such as long text and binary data (e.g. multimedia), because the data
is always loaded in a spreadsheet with relatively little space. By now, a
simple workaround is to check Edit query result instead of Show
query result in the left bottom corner of your sqleditor. Running your
query with Execute will then show only one dataset at a time, leaving
more space to read long text (even if you do not edit the text).
- The 2nd subitem in the left bottom corner of your sqleditor under Show query
result, Save query result to file, doesn't work.