SQooLer tutorial (v 0.1.0 - 0.1.2)



Set your JDBC driver
 

After you installed SQooLer you have to open its preference page. (Window -> Preferences -> SQooLer)

  • Choose your database in the combobox
  • Set up your JDBC driver

    • That's all what you need to configure before you use the plugin.

    		 alttext
    		 
     

    The SQooLer perspective
     

    Now create a simple project (e.g. "scripts"), and a simple file (e.g. "test.sql"). The file name must have the extension "sql".
    If you are done switch to SQooLer perspective.

    You have to see your project in "Navigator" and your "test.sql" in an editor, and there is a view under the editor called SQooLer.
    You have six icons in the toolbar if your editor is active:

  • New session
  • Release session
  • Run statement
  • Cancel statement
  • Commit
  • Rollback

    • Click on "New session", and fill the new session dialog with the properties of your database connection.

    		 alttext
    		 
     

    Run your first statement
     

    If you successfully connected to your database, you can see informations about in the SQooLer view, or error messages if the connecting is failed.

    Now you can write your statement in the "test.sql" (SELECT * FROM test), and click on "Run", or press "F9". The result appears in the table in SQooLer view.

    		 alttext
    		 
     

    Tips & Tricks
     

  • If you have more then one statement in the editor, select the one you want to run.

  • There is an information icon in the toolbar of view. You can see some properties of your database and JDBC driver.

  • Double click on a cell in the table opens a data viewer dialog.

  • You can configure your own hotkeys in Window -> Preferences -> Workbench -> Keys. You have to choose the category "SQooLer Actions".

  • Oracle: you can clear the field tnsnames.ora and you can type manually your connection data in the "New session" dialog.

  • There is a "properties" directory contains several text files in the plugin directory. You can modify theese files as you wish:
  • "content.properties": this file contains keywords for the content assist, and can contain help texts, too. E.g.:
    SELECT=SELECT [DISTINCT] {select-item...
  • "datatypes", "plsql", "sql_functions", "sql_keywords", "sql_statements": theese files contain words for syntax-highlighting.

    		• alttext
    		 
     

    Back