CONQUEST SOFTWARE SOLUTIONS - Tools for Oracle development, database administration, SQL and PL/SQL formatting, analysis and flowcharting oracle development tools, pl/sql gui, plsql ide, pl/sql tools, pl/sql ide, pl/sql environment, pl/sql development, plsql gui, oracle dba tools, oracle, pl/sql tool, oracle pl/sql tools

June, 09 2008

SQL*Plus built-in commands are available in code chunks.
Some kind of stand-alone SQL statements are recognized by ClearSQL, and thus can be
considered as a statement list. SQL*Plus built-in commands can appear BEFORE and AFTER
this list only, not between its items (i.e. between separate SQL statements).
The same is true for a PL/SQL code chunk.
Please note that SET TRANSACTION statement can't be the first statement in a SQL statement
list. In this case it will be considered as an SQL*Plus command and will produce an error while
parsing stage.
SQL*Plus command is available after a code chunk if and only if there is a trailing
slash (/) after PL/SQL code.

Setup program will install the "clearsql.ini" option file into
"<drive>:\Documents and Settings\<OS_user_name>\Application Data\ClearSQL".
Parser improvements: analytic functions in CASE statement.
Parser improvements: CALL, EACH, INTERVAL, KEEP, MAP, PIPE keywords.
Parser improvements: EXTRACT function.
Parser improvements: support of REFERENCE keyword in full-qualified names.
Code Editor: Line numbers added.
On the very first start the following options are set as:
- built-in preprocessor - OFF
- flowchart code - SHORTENED mode
- flowchart output - PNG
"Delete selection..." menu item was added into the flowchart list's Popup menu.

Formatting procedure puts extra commas when formatting INSERT statement
with leading commas in lists. Fixed.
Editor control fails while highlighting a line longer than 1024 chars. Fixed.
Formatting error for nested collection items access, for example
a := Collection1(idx1).item(idx2).item2(idx3).item3; Fixed.
An error in the code review rule (Mode of parameter is not specified
with IN parameter), when it was being invoked for PROCEDUREs. Fixed.
Auto correction feature for the review rule (Mode of parameter is not specified with IN parameter)
was cancelled as an error-prone procedure while comments handling.
Access Violation on shutdown procedure. Fixed.
Numbers in .123 format gave syntax errors. Fixed.
Macro substitution char ( & ) inside comments are still considered by parser. Fixed.
Single file (Manual) analysis erases the flowchart folder before its run, but it must not. Fixed.
Main code chunk is saved succesfully but version files are not while "Save Project As..."
command. Fixed.
Project Tree is not invalidated after deleting the last version of the code chunk (for multi-versions
code items only). Fixed.
After deleting the last flowchart file from the list the built-in browser still shows its picture. Fixed.

August, 09 2007

Bulk export any selection of scripts back to the file system;
Bulk import multiple files into an existing project;
Bulk import database objects (functions, procedures, packages etc.) into an existing project directly from a database;
Multiple ORACLE_HOMEs are supported. The SQL*Plus utility can be invoked from a BIN directory of the ORACLE_HOME of your choice. Default ORACLE_HOME is also supported.

April, 15 2007

Flowchart diagrams can be viewed (popup menu) in external browser (default browser).
“Auto Show Results” option added. If it is set, stored data will be shown automatically in the Analyser View (upper window) while walking the Project tree. There is a delay which the user can set (Environment Options -> Preferences) to allow a step by step walk through the tree without being interrupted by auto update of the Analyzer View.
“Save Results” option added. If it is set, results of the manual analysis are stored in an internal database and if “Auto Show Results” is on, the last analysis results are shown when project is opened again.
Drop - down list of previously opened projects added.
Error messages are stored in an internal database and can be retrieved later.
Colored status labels keep track of Analysis results (Project tree). The status of the last analyzed items are in color, any previous ones are in grey.
“Show Legend” option in Call Tree Diagram is enabled.
“Strip Out Comments” option added.

CANCEL button was added to cancel application's closing.
GOTO BOOKMARK and CLEAR BOOKMARKS popup menu items are disabled if there are no bookmarks set.
Error list in Analyzer View, may be shown in a dialog box (popup menu item) instead of being shown with a hint.
New icon set through application (main form, Analyzer Option dialog).
Status bars added to Flowchart diagrams view and Call Tree diagrams view.
Each project has a directory (folder) set of its own.
Extended description added to Checker dialog.
Button shape can be flat or regular.
“Rationale” dialog: non-standard button (on left) removed and the standard “Close” button added.
Project analysis can be cancelled by user by pushing the ESCAPE button.
A Project tree node always keeps its selection state.
Build - in registration procedure via GUI (Main menu -> Help -> Register . . . ) removed from application.
Popup menus in both browsers are the same.
Registration key as a licence file is accepted. Place registration key (licence file) in the same directory where ClearSQL resides.
(for example C:\Program Files\ClearSQL\bin).
Call tree diagrams (* . html, * . gif) are stored in a separate directory.
C:\Documents and Settings\<user_name>\Application Data\ClearSQL\<project name>\calltree.

If large display font (120 dpi) is set (under Windows XP), exiting application caused Access Violation error.
Syntax check: TRIM function accepts additional parameters.
Bug in the comments joining procedure.
Run - time error (memory leak) occurs when Manual analysis is invoked immediately after Project Analysis.
Project Tree width problem: two columns of header are shown in full.
Print preview dialog: Button caption is changed to “Fit to page”.
New panels and splitter added to Call Tree Tab view to adjust the width of drop - down lists.
If ROOT node of Project Tree is selected, “Analyze Project” button is enabled (it was disabled if no code node was selected).
Clicking on the free space of project tree unselects the previously selected (focused) tree node.
Buttons on horizontal and vertical toolbars are enabled or disabled according to project tree node type.