JBSql  1.0

A freeware enhanced Oracle SQL*Plus© replacement.

Created by Jorgen Bosman 2001-2002

1 Introduction

This program is for those of you who like the command-line interface of Oracle's SQL*Plus©,

but are tired of the limited screen output and editing capabilities.

This program is intended to keep the familiar command-line interface for rapid typing of

sql statements, but allows you to get a better query result overview and have better

text editing and command history capabilities.

This program is intended to be largely compatible with Oracle's SQL*Plus©, but not all

features have been implemented yet, and some may never be implemented...

Please check my website regularly for newer versions, because it's under constant development.

You can also contact me if you want to be notified when I upload a new version.

2 Installation

Installation is very easy, just extract jbsql.exe from the zip file and place it anywhere you want to.

To run it, you need to have the Oracle 8i client (or higher) installed on your pc and your Primary Oracle Home

must be pointing to the Oracle 8i home. Alternatively, you can extract the jbsql.exe to your %ORACLE_HOME%\bin

directory, then you don't have to worry about your Oracle Homes.

To start jbsql, just double-click the jbsql.exe file...

If you get errors like 'symbol xxx not found in oci32.dll', then you don't have the Oracle 8i home as your primary Oracle home. Use the Oracle Home Selector to change it.

If you get "ORA-24315: illegal attribute type" every time you get another Oracle error, then  you don't have the Oracle 8i home as your primary Oracle home. Use the Oracle Home Selector to change it.

3 Logging on

When you start jbsql, you will be prompted to log on to a database:

Just enter your database user name, password and database and click "OK".

This should be sufficient for most connections.

If you want access as SYSDBA or SYSOPER, select it from the dropdown list instead of NORMAL.

(Note that startup, shutdown and recover database is not supported!)

Your last 10 usernames and databases are remembered. You can quickly reuse them by selecting them from the drop-down list.

You can also quickly access a database that's not in your tnsnames.ora by filling in the hostname:port:SID in the database field.

e.g.: dbserver:1521:ORCL

This method only works for tcp/ip connections.

You can also use / as username and nothing as a password to connect using your NT username.

If you leave the database empty, then you are connected to your local database or to the database

where your LOCAL environment/registry variable is pointing to.

You can also give the connectstring as a command-line parameter. This way you can create a shortcut to your favourite database.

e.g.: jbsql.exe scott/tiger@dbserver

You can also specify an command to run when you are logged in, for example to run a sql script. Just specify the command on the commandline just after the connectstring.

e.g.: jbsql.exe scott/tiger@db @c:\temp\script.sql
or jbsql.exe scott/tiger "select 'Instance '||instance_name||' on host '||host_name instance from v$instance;"

4 Commands

4.1 Introduction

You can enter commands at the "SQL>" prompt. Oracle commands should be terminated by a ; or / character.

JBSql commands must not be terminated, but it's no error if they are terminated.

When you execute a query, the query results are displayed at the bottom in a listview. You can resize columns and scroll

through the records.

4.1 Oracle commands

You can execute all known standard Oracle DML and DDL commands, such as select, update, delete, insert, create, drop, alter ...

For most DDL commands, jbsql will tell you what it's doing and what it has done. All Oracle commands should be terminated with

the ; or / character.

For an overview of all sql statements, see http://otn.oracle.com (sql reference)

4.2 JBSql Commands

exec[ute] stored_procedure;

The execute command allows you to execute a stored procedure/function/package. 
This is identical to BEGIN stored_procedure; END;

exit

Quits JBSql

dir
ls

Shows a list of all user objects

r
/

Repeats the previous command

ed[it] [file]

Starts an external editor containing the previous command. Or when you specify a file name, it starts the editor with the specified file.

desc[ribe] object

Shows a description of the specified database object (tables, views, procedures, ...)

show err[or] [object_type object_name]

Shows the PL/SQL errors in the last created/compiled object, or the errors for the specified object.

show par[ameter] name

Shows the initialization parameters that contain name

@script [parameter1] [parameter2] ...

Runs the commands inside the specified sql script. If no extension is given, .sql is assumed.
To specify a script inside a directory that contains spaces, surround the script with " "
e.g.: @"c:\program files\jbsql\tst.sql"
If the scripts accepts parameters (&1, &2, ...), you can specify them after the script name.

@@script [parameter1] [parameter2] ...

Runs the commands inside the specified sql script. If no extension is given, .sql is assumed.
To specify a script inside a directory that contains spaces, surround the script with " "
e.g.: @"c:\program files\jbsql\tst.sql"
If the scripts accepts parameters (&1, &2, ...), you can specify them after the script name.
The double @@ looks for sql scripts inside the same directory as the calling script. So it should be
used from within another script.

spool file|off

Writes all following sql output to the specified file

off, turns off spooling and closes the file.

set option value|on|off [option value|on|off ...]

Gives a value to an option (see Options for a list of options)
You can specify multiple options at once and options may be abbreviated. If the starting characters match exactly one option, then that option is set.
set without parameters shows an overview of current option values

define variable[=value]

Gives a value to a variable. This variable can be used inside scripts by using &variable or &&variable.
If you do not specify =value, then the current value is shown.

undef[ine] variable

Removes the specified variable

acc[ept] variable [num[ber]|char|date] [for[mat] format] [def[ault] default] [prompt text|nopr[ompt]] [hide]

Prompts the user to enter a value for a variable.

Refer to the following list for a description of each term or clause:

variable

Represents the name of the variable in which you wish to store a value.

NUM[BER]

Makes the datatype of variable the datatype NUMBER. If the reply does not match the datatype, ACCEPT gives an error message and prompts again.

CHAR

Makes the datatype of variable the datatype CHAR.

DATE

Makes reply a valid DATE format. If the reply is not a valid DATE format, ACCEPT gives an error message and prompts again.

FOR[MAT]

Specifies the input format for the reply. If the reply does not match the specified format, ACCEPT gives an error message and prompts again for a reply. The format element must be a text constant such as A10 or 9.999. See the the TO_NUMBER or TO_DATE commands for a complete list of format elements.

DEF[AULT]

Sets the default value if a reply is not given. The reply must be in the specified format if defined.

PROMPT text

Displays text on-screen before accepting the value of variable from the user.

NOPR[OMPT]

Skips a line and waits for input without displaying a prompt.

HIDE

Hides the text that you type behind '*' characters.

conn[ect] username/password[@database] [as sysdba|sysoper|normal]

Creates a connection to a database with the specified credentials. If you do not specify a password, then you will be prompted for a password. For the database, you can also specify host:port:SID or host:SID or host:port for quick connections to a database.

disc[onnect]

Disconnects the current sessiom from the database. You cannot execute any sql commands anymore until you use the connect command again.

prompt [text]

Prints the given text to the console window.

tune

Puts the last executed command inside the sql analyzer window.

5 Options

5.1 Introduction

You can set various options to control the behaviour of jbsql. Options are persistent, you don't have to enter them again when you start jbsql.

All options can be configured with a dialog box and via the 'set' command.
The dialog box can be opened via the Tools->Options menu.

The list on the left shows all possible options, when you select an option, the current value is displayed on the right hand side, along with a description of the option. For boolean options (true or false), a checkbox is displayed whether or not you want to show this option on the main window's toolbar or not for easy access to this option.

5.2 Overview

allow_newline

If set, pressing Enter inside a sql statement inserts a newline. If not set, then the statement is executed.

arraysize

Specifies how many records are fetched at once. If the amount of memory that's needed to hold the records exeeds the maxmem option, then the arraysize is automatically reduced for the executed statement.

autocomplete

Specifies wheter or not autocomplete should be active when you press TAB.

autotrace

When autotrace is enabled, the execution plan is displayed in the sql analyzer window before each statement is executed and statistics about the statement are displayed after the query in the console.

commandhistory

Specifies how many previous commands are kept in memory.

directory

Specifies the startup directory for jbsql. This makes it easier to type the location of sql scripts, you only have to type the location relative to the startup directory.

editor

Specifies what editor to use with the 'edit' command.

edit_filename

Specifies what filename to create with the 'edit' command

feedback

If set, then a result is shown each time a statement is successfully processed.

heading

Should headings be printed when output to screen is enabled or spooling is on?

listview

Specifies wheter query output should appear in the listview table at the bottom or not.

long

Specifies how many characters are read from LONG, LONG RAW, BLOB, CLOB and BFILE colums.

max_scripts

Specifies the maximum number of nested scripts. This is to prevent recursive scripts.

maxlines

Specifies how many lines are buffered in the console window.

maxmem

Specifies the maximum memory usage for queries, if arraysize*record_size > maxmem then the arraysize is automatically adjusted to fit into the maximum memory usage.

prompt

Specifies the text to use as console prompt.

savehistory

Saves the command history to a file when you exit jbsql and reads them back in when you start jbsql

scan

Scan scripts for & characters, which denotes variables and ask for variable values.

screen

Is output from queries to the console on?

serveroutput

Displays output generated by dbms_output after completion of a sql statement.

sound

Play a sound when long running queries are finished.

soundfile

Specified the sound file to play.

soundtime

Specifies the time (in seconds) after which a sound should be played..

timing

If enabled, displays elapsed time information for each sql statement.

verify

If enabled, displays old and new values for replaced && variables in a script.

6 Extra features

6.1 Command recall

You can press 'arrow up' inside the console to get the previous commands back. You can use 'arrow down' to scroll between the previous commands. The previous commands are also persistent between jbsql sessions if the 'savehistory' option is enabled.

6.2 Inline editing

While you are typing a command of when you have recalled a command, you can use the 'arrow left', 'arrow right', 'home','end', 'Page Up and 'Page down' key to navigate the cursor to another position. When you're not at the end of a command and you have a multi-line command, then you can also use the 'arrow up' and 'arrow down' key to navigate to a previous line or next line inside the command.

'Home' moves the cursor to the beginning of the current line of the current command.
'End' moves the cursor to the end of the current line of the current command.
'Page Up' moves the cursor to the beginning of the command.
'Page Down' moves the cursor to the end of the command.
'Ctrl-Left' moves the cursor to the start of the previous word.
'Ctrl-Right' moves the cursor to the start of the next word.

When you're inside a command, you can insert text or use the 'del' and 'backspace' key to delete text.

When the 'allow_newline' option is on, then you can insert a new line inside the command by pressing the 'enter' key. The command is only executed when the cursor at the end of the command.

When the 'allow_newline' option is off, then pressing 'enter' will always execute the command, no matter where the cursor is. You can insert a new line in the command by pressing 'Shift-Enter'.

You can also position the cursor by clicking with the mouse at the desired position inside the current command.

6.3 Autocompletion

When you are typing a sql statement, you can press the 'tab' key to find a list of closest matches to the word that you are typing. If more that one match is found, a popup list is displayed with all possible choices. If only one match is found, then the word is automatically completed without bringing up the popup list.

The autocompletion is context sensitive, this means that is knows for example that after the 'from' word, it is likely that you want to type a table name or a view name, so it searches a list of table and view names. It does not do complete sql parsing, so it does not correlate column names after the 'where' word with table names after the 'from' word unless you give those tables an alias and also specify the alias after the where keyword. Just try it out and see what happens, most of the time, the correct list is shown, but sometimes it may not be what you expect.

Autocomplete also works for specifying script names after the @ command. It completes directory and file names.

6.4 Mouse

JBSql has got (just like SQL*Plus), rectangular selection. This means that you can select text inside the console, not line by line, but in a rectangular fashion. It also has the same quick-paste feature as SQL*Plus. This means that when you press the right mouse button after you have selected a piece of text and also while the left button is still down, the selected text is pasted at the current cursor location.

6.5 Copy-Paste

You can copy selected text from the console using Ctrl-C or Ctrl-Insert and paste text inside the console window by using Ctrl-V, or Shift-Insert.

6.6 Quick Exit

You can quickly exit jbsql by pressing Ctrl-D

6.7 Interruptable statements

You can cancel a running statement by pressinc Ctrl-X or selecting 'Cancel' from the Query menu. It may take a while before the statement is cancelled.

6.8 Multithreading

While a statement is executing, the rest of the application still responds to user input. For example, you can still select text or change an option while a query is executing. The same yields while the 'edit' command is running or when a script is running.

6.9 User friendly feedback

For most sql statements, jbsql will tell you what it's doing: parsing, executing, fetching, ...

For most create/alter statements, it will tell you which table/index/... it is creating and has created. This is most useful in scripts that contain many create/alter or drop statements. This way you can easily track errors in your scripts.

7 SQL Analyzer

The SQL Analyzer helps you to tune your sql statements. At the top, you can enter your sql statement.

If autotrace is on or if you enter the tune command, the last executed command is put at the top.

The hint listbox contains most known hints. When you select a hint from the list, a short explaination is displayed at the bottom.

Depending on the hint, the table and index list is displayed. From these lists, you can select the table name(s) and index name(s). When you have selected a hint/table/index, the sql statement is updated with the new hint. Some hints require one or more table names as parameter and some hints also require one or more index names. Remember that if you have table aliases in your sql statement, then you have to use the same aliases in your hint instead of the table name.

When you press the 'Explain plan' button, the sql statement is analyzed and the execution plan is displayed in the tree in the middle. Remember that if there's a syntax error inside the hint, Oracle doesn't complain about it.

When you press the 'Execute' button, the sql statement is copied to the console and the statement is executed. This way you can see how fast the statement executes.

8 Schema Browser

With this tool, you can see the DDL create statements for most database objects.

The top three listboxes let you choose the database object. First select the desired schema name, then the object type and then the object name. When you change the schema, the other listboxes are updated with data from the chosen schema. When you change the object type, the object name list is updated with all the object names from the chosen schema and objec type. When you have selected an object name, the DDL create statement is shown in the text window below. When you have selected a table, then it also shows the DDL create statement for the indexes and constraints on that table.

9 Export

You can export the currently selected data to a file. This feature is available from the file menu.

9.1 CSV format

When you export to CSV (Comma Separated Values) format, the delimiter is a ; character and all fields are enclosed by a " character. If there is a " inside the exported data, then to consecutive " characters are put in the csv file. All fields are exported as text and as they are shown in the list view.

9.2 XML format

You can also export the selected data to a XML file. The format of the xml file is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<ROWS>
  <ROW num="1">
    <COLUMN1>value1</COLUMN1>
    <COLUMN2>value2</COLUMN2>
    ...
  </ROW>
  ...
</ROWS>

9.3 SQL format

You can also export the selected data as a SQL insert script. This will generate sql insert statements for each row. This generated script may not always work, for example if you have a complex query. It will probably work best if you have just done select * from some_table;

10 Change history

V1.1.0.0 27/05/2003:

• Fixed bug: spooling to file and running an anonymous plsql block caused statements like 'parsing statement' to be put in the spool file.
• Added comments to describe output
• Fixed bug: export to csv now puts newline after header

V1.0.2.8 27/05/2003:

• Fixed small resizing problem with sql analyzer
• Export in csv format now also exports a heading with column names
• Added possibility to play a sound after a long running query has finished
• Added the 'sound', 'soundfile' and 'soundtime' options to support this
• Added the 'history' option. Enabling this will keep a history of all executed statements. It logs all statements in the jbsql_history.txt file in your documents and settings directory.

V1.0.2.7 26/05/2003:

• Fixed bug: 'tune' without previous command would crash
• Fixed bug: 'exit' at the end of a script without newline whould crash
• Fixed bug: spool off without first spooling corrupted screen output
• Made SQLAnalyzer window resizable + added a splitter window

V1.0.2.6 01/03/2003:

• Fixed bug: Clicking the mouse while running a command could cause the cursor to position incorrectly
• Added support for the 'WITH' statement
• Fixed bug: The 'r' command didn't insert newline characters anymore.
• Fixed bug: The ordering of the show err command was sometimes incorrect.
• Fixed bug: Pressing TAB after a '.' character now also works after a newline and after more than one occurance.
• Pressing TAB after a '.' character now also shows a list of tables if the word before the '.' is a schema name.
• Pressing TAB after select now also searches for synonyms.

V1.0.2.5 30/01/2003:

• Fixed bug: Sometimes the CTRL key was remembered incorrectly, this caused left/right keys to jump words instead of characters.
• Fixed bug: Opening a new window caused the first command the be 'AS NORMAL' followed by the typed text.
• Fixed bug: exit command did not work inside a script.
• Fixed bug: New window did not work when connected as sysdba or sysoper.
• Specifying @"script.sql" on the commandline also works now.
• Fixed bug: Paste of % character works again.

V1.0.2.4 27/01/2003:

• Improved large package parsing speed.
• dbms_output is retrieved after a sql error occured.
• no longer locks the plan_table after tuning a query.
• Added possibility to execute a command from the commandline, just enter the desired command after the connectstring on the commandline. eg: jbsql.exe scott/tiger@db @c:\temp\script.sql
  or jbsql.exe scott/tiger "select 'Instance '||instance_name||' on host '||host_name instance from v$instance;"
• The 'edit', 'tune', '/' and 'r' commands now work on the last known real sql statement. For example, they do not work on a describe statement, but they do work on a select statement.
• You can now use the mouse to position the cursor in the current command.
• 'Home' and 'End' keys now go to the start/end of the current line within the command.
• 'Page Up' now goes the the start of the current command.
• 'Page Down' now goes to the end of the current command.
• You can now enter a newline within a command by using 'Shift-Enter'.
• 'Ctrl-Right' and 'Ctrl-Left' now moves to the next/previous word.
• Scrolling left or right with the cursor now 'jump scrolls' several characters at once.
• Fixed text positioning bug when you scrolled up with the cursor and started typing.
• Fixed bug. You could not enter a select/insert/update/delete with a hint and a newline just after the last '*/'.
• Fixed bug. ';' is now ignored after '@' or 'spool' command

V1.0.2.3 13/01/2003:

• Fixed crash with schema browser when more than 1000 objects of the same type were present in a schema.
• Added support for new timestamp datatypes
• Choosing 'new window' now first saves the command history. This means that you can use the commands from the previous session in your new session.
• Added support for 'show par[ameter] name' command
• Added support for 'show err[or] [object_type object_name]'
• Added shortcut key Ctrl-N to reconnect
• Fixed redraw bug when pasting a command that changed some option on the toolbar.
• Autocompletion now also works with exec[ute] and start commands
• Autocomplete now recognizes column names and procedure names when typing TAB after a . character (still experimental)

V1.0.2.2 28/11/2002:

• Fixed a bug in running scripts that contain / within comment
• Slightly improved script running speed
• Improved schema browser speed by using array fetching
• Order by and group by now show columns when pressing the tab key

V1.0.2.1 24/09/2002:

• The export function now appends a file extention when you did not type an extention
• Fixed copy/paste problems when other windows were open (sql analyzer or schema browser)

V1.0.2.0 22/09/2002:

• Added export to csv, xml or sql file, available from the 'File' menu. It exports the currently selected data.
• You can now also abort a running script.
• You can now copy data from the list view at the bottom. When you click the right mouse button, you will get a popup menu from which you can choose to copy the entire line or just the first column.
• Added some keyboard shortcuts
• Hints for table names containing a $, now work too
• Fixed paste problem with strings beginning with #
• Added Edit menu
• Ctrl-C no longer cancels a query, instead use Ctrl-X
• Improved speed of command-parsing routines

V1.0.1.5 17/09/2002:

• Fixed bug: Running scripts without valid last command in the file didn't execute the last line and caused jbsql to behave weird.
• Fixed bug: Running a plsql block or a stored procedure that raised NO_DATA_FOUND exception caused jbsql to display an OCI error.
• When you are typing a new command or changing a previous command, and you accidentaly press arrow up, then the current command is remembered. You can retrieve the modified command by pressing arrow down button all the way to the last command.

V1.0.1.4 30/07/2002:

• Fixed bug: Starting jbsql with connectstring as command-line parameter without the password caused jbsql to hang
• Increased length of remembered usernames and databases, this may cause your lists at the logon dialog box to look weird.

V1.0.1.3 13/05/2002:

• Fixed weird behaviour when executing empty scripts

V1.0.1.2 02/05/2002:

• Listboxes no longer show a big gray block when the schema browser window is resized.
• Quick paste multiple commands at once now works
• Fixed recent introduced bug that prevented scripts that didn't have an ending newline from running.
• The edit command now appends .sql to the filename when no extension has been given and the file does not exist.
• set serveroutput on now does an implicit dbms_output.enable(100000)

V1.0.1.1 02/05/2002:

• The listboxes in the schema browser can now be used in WindowsNT/2000 too, not only WindowsXP.

V1.0.1.0 01/05/2002:

• Fixed problem with & and && variables being on a 1000 character boundary in scripts.
• Improved screen output speed when drawing the lines under the column headers.
• Added new feature: Schema Browser
  This new tool is available under the tools menu. It allows you to view the definition of most database objects. In fact, it shows the DDL create statement for the object. This tool isn't finished yet, but it should give you an idea of what it can do.

V1.0.0.6 25/04/2002:

• Improved & and && compatibility with SQL*Plus. & only asks for the variable is it's not previously defined. && doies the same thing, but does an implicit define of the variable so that it can be reused. (remember that defined variables inside a script are defined only during the duration of the script, this is different than SQL*Plus)
• No longer gives an error on 'column x format y' commands, but doesn't do anything with it...
• Added support for the 'rollback to savepoint x' command.
• Added support for the 'edit filename' command.
• Fixed hard coded 'afiedt.buf' filename.
• Fixed 'show error' on objects created with owner.object_name
• The working directory (directory option) is passed on to the external editor with the 'edit' command
• Copy-Paste now also works with Ctrl-Insert and Shift-Insert
• When a command starts with #, then the # character is stripped from the command.

V1.0.0.5 17/04/2002:

• Fixed weird disappearing console/toolbar window bug.
• Because of this, options set inside a script are only set locally to the running script. When the script ends, the original settings are restored.

V1.0.0.4 04/03/2002:

• Fixed bug when running scripts that asks for variables. Sometimes jbsql would hang when leaving the main window.
• When you choose to reconnect using the logon dialog, the currently typed statement is cleared.

V1.0.0.3 23/02/2002:

• Tune and autotrace now put sql command with newlines correctly into the sql analyzer window
• Fixed memory leak
• Added debug option, this will create a jbsql.log file with debugging information in it.

V1.0.0.2 19/02/2002:

• Autocomplete for files in current directory now works
• Fixed script nesting directory problem
• Enhanced the set command, you can now set multiple options at once by using 'set option value option value ...'
• Options can now be abbreviated, for example 'set feedb on' will turn feedback on.
• Better feedback to user when creating or dropping public synonyms
• create [or replace] type [body] support.

V1.0.0.1 07/02/2002:

• connect /@database now doesn ask password anymore
• Output buffers are no longer limited to 5000 characters, but are now dynamic. This allows you to paste sql statements with lines longer than 5000 characters
• Username and database on the logon window can now be longer than the width of the field.
  

V1.0.0.0 28/01/2002:

• Fixed set scan off bug
• Added SYSDBA/SYSOPER/NORMAL connect modes, also changed the connect command to:
  connect username/password[@database] [as sysdba|sysoper|normal]
• Added quick connect using host:port:SID or host:SID or host:port
• connect command without password asks for password
• Added support for the set constraint[s], set role and set transaction commands
• Added this documentation
  

22/01/2002:

• Errors in sql statements in the SQL Analyzer are now shown in the tree instead of in a dialog box
• Fixed copy-paste bug from SQL Analyzer to console
• The sql statement inside the SQL Analyzer is now seen as a single sql statement in the console when the Execute button is pressed
• Abbreviated the connect command to conn[ect]
• Abbreviated the disconnect command to disc[connect]
• You can now pass arguments to scripts. 
  Use &&1, &&2, ... inside the script to access them
• You can specify a script withing a directory that contains spaces by surrounding it with quotes: @"c:\program files\jbsql\tst.sql" arg1 arg2
• Autocomplete now also works with the spool command and when quotes are used to surround a filename
• Added missing jbsql.manifest file to zip file to allow you to compile it
• Changed output of 'show errors' a little bit to improve the screen appearance.

20/01/2002:

• Added 'tune' command to put the previous command into the sql analyzer
• Fixed ORA-01406 when fetching of LONG columns that are larger than the specified long size.
• The sql analyzer now does nothing when a statement is active in the console.
  Otherwise it would produce unpredictable results.

16/01/2002:

• Added SQL Analyzer tool, available from the 'Tools' menu. With this new tool, you can view execution plans for your queries and add hints to the query. You can select most hints from a listbox. For hints that require table and/or index names, listboxes will appear when necessary. In these listboxes you can select one or more tables/indexes depending on the hint. You can also exeute the tuned query with a click on a button to see the actual processing time.
• Added 'autotrace' option (only on and off). This option will automatically pop-up the SQL Analyzer window and show the query plan for the last executed query. It will also show session statistics in the console.
• Removed most 'Statement processed' and 'Executing statement' messages and replaced them with more meaningful messages.

10/01/2002:

• Fixed some problems with accept inside scripts
• Fixed wrong error position due to new verbose output
• Fixed problem with describe from a synonyn when the synonym has a different name than the actual object (thanks to Dieter Van Baarle)
• Added autocomplete when entering a script filename. Pressing <TAB> will expand directory names and filenames and show a list of matching filenames if more than one match is found.
• Reworked the screen printing in order to clean up the spaghetti code. This may result in strange behaving screen output. Please report this to me and describe how to reproduce the problem! One possible symptom is that a line which should have been on the next line, is appended to the previous line.
• Fixed screen refresh problem
• When the 'screen' option is on, the headers are no longer printed when there are no records found.
• When running a script, the 'screen' option is turned on during the duration of the script.

02/01/2002:

• Added ROWID support
• Added toolbar buttons. Also configurable via options dialog.
• Added New Window menu item. This opens a new jbsql windows with the same connection.
• Added Commit, Rollback and Repeat to menu and toolbar
• Added Windows XP visual styles
• You can now select text with the mouse that's beyond the visible window.
• & and && support in scripts (not yet on the console)
• Added 'scan' option. set scan off disabled the & and && scanning
• Added 'verify' option. set verify off disables printing old and new values when & and && have been replaced
• Added 'exec[ute]' support
• Added more verbose statement/query progress
• Query can now be cancelled when no records have been fetched yet
• 'define variable=value' support
• 'undef variable' support
• 'accept' command support
• Oracle 8.0.x client desupported, only 8i and above is supported

11/06/2001:

• Fixed bug when running scripts that contained /* */ within create [or replace] ... statements
• Fixed bug when saving command history that caused the last character of statements that were not terminated by ; or / to be repeated twice
• Fixed 2 memory leaks

07/06/2001:

• Fixed possible typing before logon screen appeared
• Added command expansion (autocomplete) and tooltips: Pressing <TAB> when you've typed one or more letters does a context sensitive (not perfect) match for the words that match the typed word. If only one is found, then the partially typed word is completed with the found word. If more matches are found, then a list with the matches is displayed, so that you can choose one.
• Added autocomplete option to turn this fancy feature on or off
• Fixed the funny animated column resizing in the list view when you have many columns, should be faster too.
• Fixed describe of private synonym (used to say 'feature not implemented')
• Fixed describe of public synonym where a private synonym existed for another user with the same name. Then that table would sometimes be described instead of the public synonym table.

08/05/2001:

• Fixed crash when executing a query after 'connect' command
• Changed location of registry settings to HKEY_CURRENT_USER. This allows per user settings instead of global settings.
• Logon dialog box shows 10 last usernames and databases and fills these fields with the last used values.

03/05/2001:

• Fixed new tokenizer bug of previous release that caused newlines within sql commands not
  to work in all cases
• Fixed 'allow_newline' bug of previous release that caused the display to be corrupted
• Added 'rem' command
• Added 'editor' option to specify what editor to use for the 'edit' command
• Added 'edit_filename' option to specify what filename to use for the 'edit' command
• '/' command doesn't repeat the sql command again
• Added 'serveroutput' option to display dbms_output generated messages
• Added 'commandhistory' option to specify the number of previous commands to keep in memory
• Added 'savehistory' option. If turned on, then the command history is saved to a file when you exit jbsql (%WINDIR%\jbsql.his). When you start jbsql again, the command history is read from the file. This way you can use arrow up between sessions.

01/05/2001:

• Added Generic Option Dialog box
• Save options to registry \\HKLM\Software\JBSQL
• All options also settable via 'set' command
• Added 'directory' option to let jbsql change to that directory on startup (for easy script execution)
• Added 'arraysize' option to specify the number of records fetched in block
• Added 'long' option to set the number of bytes read from a LONG, LONG RAW,BLOB, CLOB or BFILE
• Added 'max_scripts' option to specify the maximum number of nested scripts.
• Added 'maxlines' option to specify the number of text lines in the console window that are buffered.
• Added 'maxmem' option to specify the maximum memory usage during a query. This will automatically adjust the array size if memory usage would be too large.
• Added 'prompt' option that allows you to set a new prompt in the console
• Moved the 'output to screen' menu item to an option.
• Added 'timing' option to display timing information for each sql command.
• Added 'connect' and 'disconnect' commands.
• Added 'connect' and 'disconnect' in file menu.
• You may now pass connect information on the commandline: jbsql.exe scott/tiger@db
• Added the current connection information to the window title.
• Fixed a NULL value BLOB, CLOB, BFILE bug
• Added 'feedback' option to turn off sql result feedback
• Added 'heading' option to turn off row headers
• Added 'spool file' 'spool off' functionality
• You can now use " " to specify an option value that includes spaces, useful for 'set directory "c:\program files\jbsql"'
• Added 'allow_newline' option. If set, pressing Enter inside a sql statement inserts a newline. If not set, then the statement is executed.
• Added 'listview' option. This turns query output in the list view at the bottom on or off.
• Added /* */ comment support in scripts ( must be the first and last characters of a line )

10 Contact

You can contact me for any questions, bugs, enhancement requests, congratulations, postcards… at the following coordinates:
If you want to thank me, please have a look at my goodies whishlist!

jorgen.bosman@pandora.be (home)
jbosma@ferranti.be (work)

Home address:
Jorgen Bosman
Groot Hagelkruis 179F
2030 Antwerpen
Belgium


You can always find the latest version (and other tools) at:
http://users.pandora.be/jbosman/applications.html

The direct download link for jbsql is:
http://users.pandora.be/jbosman/jbsql.zip

This is Freeware!