SQL Edit 32 FAQ Documentation - Frequently Asked Questions
Contents

About SQL Edit 32

  • What is SQL Edit 32 ?
  • Who should use SQL Edit 32 ?
  • Why did you develop this application ?
  • What are the most important advantages with SQL Edit 32 ?

    • Is it possible to . . . 
  • Is it possible to connect to an Oracle instance using SQL Edit 32 ?
  • Is it likely that I will have use of SQL Edit 32 working as a client applications designer?

    • How do I  . . . 
  • How do I start using SQL Edit 32 most rapidly? What are the most timesaving features?
  • How do I check to see if there exists a newer version of SQL Edit 32.
    		•

     
     
     
    About SQL Edit 32
    Q. What is SQL Edit 32 ?

    A. SQL Edit 32 is an editor containing PL/SQL code, SQL building blocks, scripts and examples of Oracle DDL commands.
    Q. Who should use SQL Edit 32 ?

    A. Anyone who wants to have quick access to Oracle SQL constructs for developing Oracle applications or administrating an Oracle database.
    Q. Why did you develop this application ?

    A. After working as a consultant and Oracle developer for a while I had a lot of scripts and code snippets all around. For me there were two reasons for saving the code and SQL DDL commands for future use:

    1. The scripts did something general and clever.

    2. I tended to forget the exact SQL syntax for seldom used commands and constructs.I also noticed that I retyped the same PL/SQL code time after time. I'll make a program that does the typing for me, I thought. Suddenly, there was SQL Edit 32.
    Q. What are the most important advantages with SQL Edit 32 ?

    A. The most important advantages of the SQL edit 32 approach are:

    1. Less frequent consultation of any SQL syntax manual.

    2. Promotion of top down programming. Concentrate on the programming instead of the typing. This also includes matching of e. g. BEGIN-END pairs and IF-THEN-ELSE.

    3. Good overview. Operations on database objects are sorted on object type.

     
     
     
    Is it possible to . . . 
    Q. Is it possible to connect to an Oracle instance using SQL Edit 32 ??

    A. NO. SQL Edit in intended for use in conjugation with a terminal tool used for connecting to Oracle, e. g. SQL*Plus.
    Q. Is it likely that I will have use of SQL Edit 32 working as a client applications designer?

    A. If you use an Oracle development tool as Developer Forms or Reports I think the answer is 'Yes'. Then you might draw advantage of the PL/SQL constructs and building blocks. With Oracle, it is very often just a design choice to put an object (function, procedure, package) on the client or on the server.

    You will not be using the DBA and trigger creating functionality though.

     
     
     
    How do I . . . 
    Q. How do I start using SQL Edit 32 most rapidly? What are the most timesaving features?

    A. That depends of course on who you are and what you want to do, but I think these are quite general features:

    First check the 'Create' and the 'Block' menu. Here you will find examples of DDL commands for creating database objects. Use these as templates for you own objects.

    You may try this as an first example:Select 'New' from menu 'File'.

    Select 'Procedure' on the 'Create' menu. Put the cursor below the line saying 'DECLARE'. Then select 'Cursor Is' from the 'Blocks' menu. Put the cursor below the line containing 'BEGIN'. Select 'Cursor Loop' from the 'Block' menu. Remove unused code and add some code of your own. You have made a DDL script for creating a procedure in five mouseclicks and a minimal amount of typing.The 'Edit' menu contains some tailored commands for making DDL (Data Definition Language) and DML (Data Manipulation Language) scripts, namely 'End Line With Comma', and 'Strip Trailing Whitespace'. These commands do not work properly in the current version of SQL Edit 32. This will soon be corrected.
    Q. How do I check to see if there exists a newer version of SQL Edit 32.

    A. Select 'Check For Update' on the 'Help' menu.