FAQ

This is a special problem of the used JDBC driver. Because of architecture needs it cannot be replaced.

Workaround: Indicate the Eclipse start parameters -Duser.language=... and -Duser.country=.... The thread 1098480 of the OTN discussion forum give more details to the problem as well as further recommendations.

With some databases whilst using jOra to execute SQL commands or stored procedures, Eclipse does not respond to user actions for several minutes. The problem occurs in particular with databases with large numbers of database-objects (stored procedures, tables, views etc.).

Unlike other database tools, in order to access lists of database objects and their properties jOra does not make use of the JDBC-driver meta-data, but directly accesses the database's system-catalog. The following views are frequently used: SYS.ALL_OBJECTS, SYS.ALL_PROBE_OBJECTS, SYS.ALL_ALL_TABLES and SYS.ALL_TRIGGERS. A simple request with SELECT * FROM [view] can be used to diagnose whether the access to the system catalog views are the cause of a performance problem.

In most cases the solution is to update the database statistics by calling DBMS_STATS.GATHER_SCHEMA_STATS('SYS').

The file extensions to be used can be configured in the Eclipse preferences.

1. Open Window->Preferences in the menu
2. Open in the entry General Content Types
3. On the left select and extend PL/SQL and SQL files
4. For every file type used by jOra an entry exists and can be linked with a file extension. Using Add further ones can be defined. Actually only one further entry for a file type is reasonable. Otherwise for jOra the file extension to be used is ambiguous.
5. To assign the new file extension with the editor which opens the file click at the link File Associations.
6. Add the new file extension with the button Add next to the list of the File Types.
7. Select the new file extension in the list
8. Assign the editor to be used with the button Add next to the list of the Associated Editors
   • SQL Script Editor for all SQL scripts
   • PL/SQL Editor for all other files (e.g. packages, views, trigger etc.)

The encoding of all file types can be configured in the Eclipse preferences.

1. Open Window->Preferences in the menu
2. Open in the entry General Content Types
3. On the left select and extend PL/SQL and SQL files
4. Enter the desired encoding in the field Default encoding (e.g. UTF-8)
5. Press button Update to make the change effective.

This changes the encoding of all file types used by jOra. To change the encoding for only some file types select the appropriate ones underneath PL/SQL and SQL files.

PL/Doc is a special kind of formating of comments in procedures, functions and packages. The syntax is quite alike Javadoc.

jOra highlights PL/Doc comments and supports the writing of PL/Doc by code completion. The PL/Doc of a selected database object is shown in the PL/Doc View. So it is always available.

Example:

create or replace package bookEntry
/**
 * The header comment describes the goal of the package.
 * 
 * @author t. lorbeer
 * @since 1.0
 */
as
   /**
    * This is the description for the first procedure in this package.
    * 
    * @param bookingDate
    *    the booking date
    *    
    * @see getBookingDate
    * 
    * @exception date_is_null
    *    occurse when <i>bookingDate</i> is null.
    */
   procedure setBookingDate(bookingDate date);
   
   /**
    * Gets the booking date.
    * 
    * @return The booking date or <code>null</code>.
    */
   function getBookingDate() return date;
end;
/
     

The following list gives an overview of all keywords and their meaning:

Furthermore all HTML tags can be used in a PL/Doc. Actually they should not be used to much. Writing PL/Doc can be quite time-consuming otherwise.

To define the default connection of a project it must have the nature "de.tl.jora.JoraNature". There are two ways to get such a project:

1. Create a new project with File/New/Project and select the project kind jOra Project.
2. For existing projects the nature can also be entered directly in the file .project:

   <projectDescription>
     ...
     <natures>
       <nature>de.tl.jora.JoraNature</nature>
     </natures>
   </projectDescription>
   	

Afterwards in the project properties one of the konfigured connections can be chosen as default connection.

Use the standard Eclipse Keys Preferences page to define or change keyboard short cuts for jOra.

Example: use CTRL+ENTER to execute SQL commands

1. Open the Preferences Page (Windows->Preferences)
2. Select General/Keys
3. Find and select the command (e.g. type filter text = 'sql')
4. Enter the new key Binding (e.g. CTRL+ENTER) and check for conflicts