Contents

1. New Features SQL Developer 1.2
2. Known Issues
3. Accessibility Issues
4. Globalization
5. Other
   

1.  New Features: SQL Developer 1.2

• Oracle SQL Developer Migration Workbench
  • Full integration with SQL Developer means that users have one tool to browse third-party databases, migrate selected objects to Oracle and then work with them.
  • Quick Migration Wizard offers least privilege migration i.e No DBA privilege is required.
  • Step driven migration offers control at each stage of the migration process.
  • Fine grain migration support provides users with the ability to select specific objects for migration.
  • Complex object migration supports stored procedures, triggers and views.
  • Translation Scratch Editor offers single statement migration.
  • Translation Difference Viewer provides side by side comparison by matching statements and blocks.


• Oracle APEX 3.0.1 (Oracle APEX 3.0.1 is scheduled for release in 2007)
  • Connect to and browse all Oracle APEX applications associated with a database schema (At application and page level)
  • Run a number of reports that allow users to report on Workspaces, Applications, Pages and Schemas
  • Export and Import Oracle APEX applications using a context menu

2.  Known Issues

• General
• Worksheet
• Connections
• PL/SQL
• Query Builder
• Import/Export
• Linux Only
• Oracle 8.1.7 (Not Certified)
• Vista
• Migration Workbench

2.1  General

• On installation, if you use Check For Updates, SQL Developer does 2 restarts. If it does not do the second restart, you must restart SQL Developer. Failure to do so, means the SQL Worksheet and Objects tab fail to initialize.
• You can't invoke SQL*Plus for tnsnames connections.
• NLS settings are not used for BINARY_FLOAT/BINARY_DOUBLE
• NLS Snippets ->EDIT multi byte CHARS show garbled data.
• EXCEL import into table doesn't work if you don't complete all the tabs in order
• Can't CREATE USER, when using users other than SYSTEM or SYS, although they have the correct privileges.

2.2 Worksheet

• Describe table@db_link gives an error that the object does not exist
• If blob column is mandatory, insert into row fails on commit

2.3  Connections

• Cannot connect to remote database as externally authenticated accounts

2.4 PL/SQL

• Problem viewing cursor value in debug mode
• Save as not working properly for package spec and body with extensions pks & pkb

2.5  Query Builder

• The Where Clause context menus only display on Mouse Over, otherwise there is only the shadow border.

2.6  Import / Export

• Cannot create correct sql*loader file for spatial data

2.7  Linux Only

• Browsing - Views > Data Tab - Actions is not working.

2.8  Oracle 8.1.7

• SQL Developer is only certified for Oracle database 9.2.0.1 and above but we do have limited 8.1.7 functionality.
• SQL tab and Export from 8.1.7 does not work

2.9  Vista

• Debug fails in Vista

2.10  Migration Workbench

• The Scratch Editor for MySQL does not support statement level translations.
• Quick Migrate on a previously created repository can fail
• Filtering not working correctly during language translation

3.  Accessibility Issues

The following is a list of known issues regarding accessibility using JAWS. The testing was done using JAWS version 5.10.

• Connections > New Connection - dialog box not read
• Connections - tree structure not read
• Tables > Create Table - buttons not read
• Data > Edit - buttons not read in edit value dialogue box
• Other User > Create User - not all items read
• Other User > Drop User - SQL statement under sql tab not read
• Any Object > right click - context menu not read
• Any Object - many tabs and details not read
• SQL Worksheet > right click table name > describe - contents of dialog box not read
• SQL Worksheet - query results not read
• SQL Worksheet > Query Builder - dialog box not read
• SQL Worksheet > right click - context menu not read
• View > Snippets - snippet details not read
• Tools > Export DDL > Options - checked options not read
• Help > Check for Update - dialog box not read
• Help - dialog and text not read
• General - menus not read
• General - toolbars not read
• General - main window title not read
  

4.  Globalization

4.1  Character Set Support

SQL Developer can connect to an Oracle Database irrespective of the database character set and the database national (NCHAR) character set. All functionality which does not involve entering or displaying characters outside of the ASCII character set is expected to work correctly with any such database.

Due to bug #5088284 in the JDBC 10.2 driver, the database character set ZHT16HKSCS31 is currently not supported.

Support for displaying and entering characters in scripts outside of the ASCII repertoire is limited to those fulfilling the following conditions:

• The character belongs to the database or to the national character set, depending on the data type of the value containing the character, and
• The script to which the character belongs is supported by the JRE installation on which SQL Developer is running, for example, appropriate fonts are available, and
• The script does not require complex rendering, e.g. it is written left-to-right with no ligatures or character reordering.

Complex scripts, like Arabic, Hebrew, or Devanagari may work in many places, but they have not been tested and they are not guaranteed to work reliably. For bidirectional scripts, e.g. Arabic and Hebrew, no functionality is provided to right-align displayed columns, nor to set directionality. Full support for those languages is planned for a future release.

SQL Developer version 1.2 is available with English user interface only. If the locale of the operating system is not English, a few UI elements, like default wizard buttons and Oracle error messages, may show up in the language of this locale. If the locale of the operating system is Japanese, part of the user interface will appear in Japanese. These translations come from the framework on which SQL Developer is built. Full translation into selected languages is planned for a future release.

This version of SQL Developer has the following globalization issues:

5.  Other


To turn on debug messages:

Edit ide/sqldeveloper/bin/sqldeveloper.conf and comment out the line:

IncludeConfFile sqldeveloper-nondebug.conf and add this line:

IncludeConfFile sqldeveloper-debug.conf