http://cc.embarcadero.com/Products.aspx?prodid=10 CodeCentral Blackfish SQL Submissions http://cc.embarcadero.com/Item/26550 2009-01-17T03:04:18 2009-01-17T03:04:18 http://cc.embarcadero.com/Item/26550 <P>Blackfish™ SQL is a high-performance, small-footprint, SQL-92 compliant transactional database. Blackfish SQL runs on both the .NET framework and on the Java platform. Database files are compatible between the two platforms.<P><B>Download the software and request your trial license</B><BR>1. Click the Download button to download the software<BR>2. Enter your information and click the Send Activation/Confirm button to receive your 30-day trial license by email <P><B>How to purchase deployment licenses</B><BR>When you're ready to deploy Blackfish SQL with your apps, see the <a href="http://www.codegear.com/products/blackfish">Blackfish SQL product page</a> for deployment license pricing options which include individual deployment licenses and deployment licenses that are included with JBuilder 2008.<P><B>New in Blackfish SQL 8</B> <UL><LI>Database triggers written in Java or any .NET language <LI>Unlimited deployment licenses available with the purchase of JBuilder 2008 Professional or Enterprise <LI>Delphi dbExpress Win32 driver can connect to Blackfish SQL for Java or .NET server; providing access for native Delphi and C++ applications <LI>Blackfish SQL ADO.NET 2.0 driver can connect to either a Blackfish for Java or .NET server <LI>Integration into Delphi Data Explorer using dbExpress or ADO.NET drivers <LI>Select statement support for retrieving autoincrement values System properties. See com.borland.datastore.driver.cons.System <LI> Additions to DB_ADMIN built-in administrative stored procedures, primarily for metadata and new licensing </UL>See the included Blackfish SQL Developer's Guide for additional information<P>Blackfish SQL for .NET is only available bundled with Delphi 2007 or later, C++Builder 2007 or later and CodeGear RAD Studio 2007. http://cc.embarcadero.com/Item/25558 2008-08-29T20:37:25 2008-08-29T20:37:25 http://cc.embarcadero.com/Item/25558 <P>Blackfish™ SQL is a high-performance, small-footprint, SQL-92 compliant transactional database. Blackfish SQL runs on both the .NET framework and on the Java platform. Database files are compatible between the two platforms.<P><B>Download the software and request your trial license</B><BR>1. Click the Download button to download the software<BR>2. Enter your information and click the Send Activation/Confirm button to receive your 30-day trial license by email <P><B>How to purchase deployment licenses</B><BR>When you're ready to deploy Blackfish SQL with your apps, see the <a href="http://www.codegear.com/products/blackfish">Blackfish SQL product page</a> for deployment license pricing options which include individual deployment licenses and deployment licenses that are included with JBuilder 2008.<P><B>New in Blackfish SQL 8</B> <UL><LI>Database triggers written in Java or any .NET language <LI>Unlimited deployment licenses available with the purchase of JBuilder 2008 Professional or Enterprise <LI>Delphi dbExpress Win32 driver can connect to Blackfish SQL for Java or .NET server; providing access for native Delphi and C++ applications <LI>Blackfish SQL ADO.NET 2.0 driver can connect to either a Blackfish for Java or .NET server <LI>Integration into Delphi Data Explorer using dbExpress or ADO.NET drivers <LI>Select statement support for retrieving autoincrement values System properties. See com.borland.datastore.driver.cons.System <LI> Additions to DB_ADMIN built-in administrative stored procedures, primarily for metadata and new licensing </UL>See the included Blackfish SQL Developer's Guide for additional information<P>Blackfish SQL for .NET is only available bundled with Delphi 2007 or later, C++Builder 2007 or later and CodeGear RAD Studio 2007. http://cc.embarcadero.com/Item/25559 2008-08-29T20:37:00 2008-08-29T20:37:00 http://cc.embarcadero.com/Item/25559 <P>Blackfish™ SQL is a high-performance, small-footprint, SQL-92 compliant transactional database. Blackfish SQL runs on both the .NET framework and on the Java platform. Database files are compatible between the two platforms.<P><B>Download the software and request your trial license</B><BR>1. Click the Download button to download the software<BR>2. Enter your information and click the Send Activation/Confirm button to receive your 30-day trial license by email <P><B>How to purchase deployment licenses</B><BR>When you're ready to deploy Blackfish SQL with your apps, see the <a href="http://www.codegear.com/products/blackfish">Blackfish SQL product page</a> for deployment license pricing options which include individual deployment licenses and deployment licenses that are included with JBuilder 2008.<P><B>New in Blackfish SQL 8</B> <UL><LI>Database triggers written in Java or any .NET language <LI>Unlimited deployment licenses available with the purchase of JBuilder 2008 Professional or Enterprise <LI>Delphi dbExpress Win32 driver can connect to Blackfish SQL for Java or .NET server; providing access for native Delphi and C++ applications <LI>Blackfish SQL ADO.NET 2.0 driver can connect to either a Blackfish for Java or .NET server <LI>Integration into Delphi Data Explorer using dbExpress or ADO.NET drivers <LI>Select statement support for retrieving autoincrement values System properties. See com.borland.datastore.driver.cons.System <LI> Additions to DB_ADMIN built-in administrative stored procedures, primarily for metadata and new licensing </UL>See the included Blackfish SQL Developer's Guide for additional information<P>Blackfish SQL for .NET is only available bundled with Delphi 2007 or later, C++Builder 2007 or later and CodeGear RAD Studio 2007. http://cc.embarcadero.com/Item/25556 2008-08-29T20:36:26 2008-08-29T20:36:26 http://cc.embarcadero.com/Item/25556 <P>Blackfish™ SQL is a high-performance, small-footprint, SQL-92 compliant transactional database. Blackfish SQL runs on both the .NET framework and on the Java platform. Database files are compatible between the two platforms.<P><B>Download the software and request your trial license</B><BR>1. Click the Download button to download the software<BR>2. Enter your information and click the Send Activation/Confirm button to receive your 30-day trial license by email <P><B>How to purchase deployment licenses</B><BR>When you're ready to deploy Blackfish SQL with your apps, see the <a href="http://www.codegear.com/products/blackfish">Blackfish SQL product page</a> for deployment license pricing options which include individual deployment licenses and deployment licenses that are included with JBuilder 2008.<P><B>New in Blackfish SQL 8</B> <UL><LI>Database triggers written in Java or any .NET language <LI>Unlimited deployment licenses available with the purchase of JBuilder 2008 Professional or Enterprise <LI>Delphi dbExpress Win32 driver can connect to Blackfish SQL for Java or .NET server; providing access for native Delphi and C++ applications <LI>Blackfish SQL ADO.NET 2.0 driver can connect to either a Blackfish for Java or .NET server <LI>Integration into Delphi Data Explorer using dbExpress or ADO.NET drivers <LI>Select statement support for retrieving autoincrement values System properties. See com.borland.datastore.driver.cons.System <LI> Additions to DB_ADMIN built-in administrative stored procedures, primarily for metadata and new licensing </UL>See the included Blackfish SQL Developer's Guide for additional information<P>Blackfish SQL for .NET is only available bundled with Delphi 2007 or later, C++Builder 2007 or later and CodeGear RAD Studio 2007. http://cc.embarcadero.com/Item/25557 2008-08-29T20:35:42 2008-08-29T20:35:42 http://cc.embarcadero.com/Item/25557 <h1 align="center"><a name="_top_"></a>JDataStore 7.06 (build 7.006.039) for Mac OS X<br>Release Notes</h1><p>These Release Notes provide a brief description of each new feature in JDataStore 7.The <cite>JDataStore Developer's Guide</cite> includes a "What's New" chapter that provideslinks to the documentation for each new feature within the Developer's Guide.</p><p><strong>Bug fix list</strong></p><ul><li>To see bugs fixed in JDataStore 7.06 click <a href="#fixed_706">here</a></li><li>To see bugs fixed in JDataStore 7.05 click <a href="#fixed_705">here</a></li><li>To see bugs fixed in JDataStore 7.04 click <a href="#fixed_704">here</a></li><li>To see bugs fixed in JDataStore 7.03 click <a href="#fixed_703">here</a></li><li>To see bugs fixed in JDataStore 7.02 click <a href="#fixed_702">here</a></li><li>To see bugs fixed in JDataStore 7.01 click <a href="#fixed_701">here</a></li></ul><p><strong>New Features</strong></p><ul><li><a href="#failsafe">The JDataStore High Availability Server: incremental backup, automatic failover</a></li><li>The new <a href="#console">Server Console</a> graphical interface</li></ul><p><strong>New SQL functions</strong></p><ul><li><a href="#bit_length"><code>BIT_LENGTH</code></a></li><li><a href="#case_function"><code>CASE</code></a></li><li><a href="#coalesce"><code>COALESCE</code></a></li><li><a href="#current_role"><code>CURRENT_ROLE</code></a></li><li><a href="#current_user"><code>CURRENT_USER</code></a></li><li><a href="#db_admin"><code>DB_ADMIN</code></a></li><li><a href="#DB_UTIL"><code>DB_UTIL</code></a></li><li><a href="#nullif"><code>NULLIF</code></a></li><li><a href="#octet_length"><code>OCTET_LENGTH</code></a></li><li><a href="#user_function"><code>USER</code></a></ul><p><strong>New and updated SQL statements</strong></p><ul><li><a href="#create_schema"><code>CREATE SCHEMA</code></a>, <a href="#drop_schema"><code>DROP SCHEMA</code></a></li><li><a href="#create_view"><code>CREATE VIEW</code></a>, <a href="#alter_view"><code>ALTER VIEW</code></a>, <a href="#drop_view"><code>DROP VIEW</code></a></li><li><a href="#create_role"><code>CREATE ROLE</code></a>, <a href="#set_role"><code>SET ROLE</code></a>, <a href="#drop_role"><code>DROP ROLE</code></a></li><li>New <code><a href="#create_table">CREATE TABLE</a></code> options</li><li>New <code><a href="#alter_table">ALTER TABLE</a></code> options</li><li>New <code><a href="#drop_table">DROP TABLE</a></code> options: <code>CASCADE</code> and <code>RESTRICT</code></li><li><a href="#create_java_class"><code>CREATE JAVA_CLASS</code></a>, <code><a href="#drop_java_class">DROP JAVA_CLASS</a></code></li></ul><p><strong>Security management</strong></p><ul><li><code><a href="#grant_statement">GRANT</a></code> and <code><a href="#revoke_statement">REVOKE</a></code></li><li><code><a href="#create_user">CREATE USER</a></code>, <code><a href="#alter_user">ALTER USER</a></code>, <code><a href="#drop_user">DROP USER</a></code></li></ul><p><strong>Transaction management</strong></p><ul><li><code><a href="#set_transaction">SET TRANSACTION</a></code></ul><p><strong>Other new SQL</strong></p><ul><li><a href="#keywords">New keywords</a></li><li>New data type: <a href="#tinyint"><code>TINYINT</code></a></li><li>Many new <a href="#escape_functions">JDBC escape functions</a></li><li><a href="#isql">ISQL cross-platform SQL command-line utility</a></li></ul><p><strong>Product notes</strong></p><ul><li><a href="#choose">Choosing between Server Console and JdsExplorer</a></li><li><a href="#change_copy">A change to the "Copy JDataStore" menu item</a></li></ul><p><strong>New and updated documentation</strong></p><ul><li><a href="#new_chaps">New chapters</a></li><li><a href="#escape">Escape syntax for calling stored procedures</a> is now documented.</li><li>Updated documentation on <a href="#jdbc_resultset">returning JDBC ResultSets</a></li></ul><p><strong>Getting started with JDataStore 7</strong></p><ul><li><a href="#migration">Migrating older databases to JDataStore 7</a></li><li><a href="#jb_bes">Using JDataStore 7 with JBuilder and the Borland Enterprise server</a></li></ul><!-- <p><a href="#bugs">Defects fixed in JDataStore 7</a></p> --><!-- <h2><a name="features"></a>New features</h2> --><h2><a name="features"></a>New features</h2><h3><a name="failsafe"></a>The JDataStore High Availability Server</h3><p>JDataStore 7 provides tools for creating automatic or manual incremental backups and for creating automatic failover to a mirror of the original database in case of failure. In addition, there are tools for viewing and managing connections on a remote server, for managing datasources and connections graphically or with the new ISQL feature, for viewing database status logs and transactions logs, for viewing logs, and for verifying databases.</p><p>The "High Availability Server" topic in the "Architecture" chapter of the <cite>JDataStore Developer's Guide</cite> discusses the architecture of JDataStore's new failsafe server and its associated mirroring functionality. This section is well worth reading, because it will help you make the most of this new offerings. </p><p>For a description of how to use JDataStore's new Server Console to access this new functionality, see the new "JDataStore Server Console" chapter in the <cite>JDataStore Developer's Guide</cite>. </p> <h3><a name="console"></a>The new Server Console graphical interface</h3><p>There is a whole new graphical interface in JDataStore 7. The Server Console performs many server administration tasks, including several that are new in JDataStore 7, such as automatic failover and incremental backup.</p><p>Here is an overview of what you can do with the Server Console. The items in the following list are topics in the "JDataStore Server Console" chapter of the <cite>JDataStore Developer's Guide</cite> for details.</p><ul><li><strong>Overview</strong> Get a quick overview of what you can do with Server Console</li><li><strong>About datasources</strong> If you're not familiar with how JDataStore uses dataasources to connect to databases, this is the place to find out.</li><li><strong>What you see and what you get</strong> Get familiar with the new Server Console interface.</li><li><strong>Starting/shutting down the server</strong> You can use Server Console to start and stop the local server.</li><li><strong>Connection settings</strong> A detailed description of how to create, modify, and delete datasources, and how to connect to and disconnect from them.</li><li><strong>Creating and managing datasources</strong> Create, rename, and modify datasources, connect to them, and disconnect from them.</li><li><strong>Verifying a database</strong> Server Console makes it easier than ever.</li><li><strong>Managing connections</strong> View and optionaly terminate both local and remote datasources.</li><li><strong>Managing database properties</strong> See an editable grid of database properties for both local and remote connections.</li><li><strong>Viewing table and row locks</strong> Server Console makes it easy to see what's happening with locks on both the local and remote server.</li><li><strong>Viewing the database status log file</strong> You exactly what's been going on with a server by viewing its server status file.</li><li><strong>Failover</strong> and <strong>incremental backup</strong> Use mirrors to protect against failures and to incrementally backup your data on a schedule of your choosing. Using Server Console, you can add </li><li><strong>Interactive SQL</strong> A special SQL pane lets you run SQL or SQL scripts against connected datasources.</li></ul><p><strong>What happened to the old JdsServer graphical interface?</strong> It's still there, but it has been replaced by the new Server Console. You can still start the JDataStore server as an application by running the <code>JdsServer</code> executable. However, it is now set to run without the GUI. If you really need that deprecated interface back, you can invoke the GUI by executing the following command:</p><table class="pre"><tr><td><pre>jdsserver -ui [windows|motif|metal|none][other parameters]</pre></td></tr></table><p>Choose the interface that is appropriate for your platform. For more about starting the JDataStore server, see "Launching JdsServer" in the "JDataStore Administration" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="keywords"></a>New keywords</h3><p>The asterisk following a keyword indicates that the keyword is <em>reserved</em>. Reserved keywords can be used as SQL identifiers only if they are enclosed in double quotation marks. When quoted in this fashion, they are case sensitive. The words that have no asterisk are <em>nonreserved</em> keywords. They can be used with or without double quotes and are case insensitive when note in quotes.</p><p>For a complete list of keywords, see <strong>Keywords</strong> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><table border="0"><tr><td>ADMIN*<br>ADMINISTRATOR*<br>AUTHORIZATION*<br>BIT_LENGTH*<br>COALESCE*<br>CURRENT_ROLE*<br>CURRENT_USER*<br>EXECUTE*<br>GRANT*<br>ISOLATION*<br></td><td>LEVEL*<br>NONE*<br>NULLIF*<br>OCTET_LENGTH*<br>ONLY*<br>OPTION*<br>PRIVILEGES*<br>PUBLIC*<br>READ<br>RENAME*<br></td><td>RESOLVABLE*<br>REVOKE*<br>ROLE<br>SCHEMA*<br>STARTUP*<br>TO*<br>TRANSACTION*<br>VIEW*<br>WITH*<br>WRITE<br></td></tr></table> <h2><a name="new_funcs"></a>New SQL functions</h2><h3><a name="bit_length"></a>BIT_LENGTH</h3><p>The <code>BIT_LENGTH</code> function gives the length in bits of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>BIT_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="case_function"></a>CASE</h3><!--BNDX="CASE function;SQL functions:CASE"--><p>The <code>CASE</code> function returns a conditional value. For more information, see <code>CASE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="coalesce"></a>COALESCE</h3><!--BNDX="COALESCE function;SQL functions:COALESCE;non-NULL values, returning"--><p>The <code>COALESCE</code> function returns the first non-NULL value from the expression list. For more information, see <code>COALESCE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="current_role">CURRENT_ROLE</a></h3><!--BNDX="CURRENT_ROLE function;SQL functions:CURRENT_ROLE;roles"--><p>The <code>CURRENT_ROLE</code> function returns the current role, or NULL if no role has been set using the <code>SET ROLE</code> statement. For more information, see <code>CURRENT_ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. </p><h3><a name="current_user"></a>CURRENT_USER</h3><!--BNDX="CURRENT_USER function;SQL functions:CURRENT_USER"--><p>The <code>CURRENT_USER</code> function returns the name of the current user. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="db_admin"></a>DB_ADMIN: administration functions</h3><!--BNDX="DB_ADMIN function;SQL functions:DB_ADMIN"--><p><code>DB_ADMIN</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. Use <code>DB_ADMIN</code> for various database administration tasks such as automatic failover, incremental backup, creating and managing datasources, viewing and managing connections, verifying tables, and displaying database privileges and properties, locks, status logs, procedure privileges, and roles granted.</p><p><code>DB_ADMIN</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method, implemented as a SQL function. The description of each method includes a link to the exact implementation and <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_ADMIN</code> provides the following methods:</p><table border="0" cols="3"><tr><td><code>ALTER_DATABASE<br>ALTER_MIRROR<br>ALTER_MIRROR_SCHEDULE<br>CLOSE_CONNECTION<br>CREATE_MIRROR<br>CREATE_MIRROR_SCHEDULE<br>DROP_MIRROR<br>DROP_MIRROR_SCHEDULE<br>GET_CONNECTIONS<br>GET_DATABASE_PRIVILEGES<br>GET_DATABASE_PROPS<br>GET_DATABASE_STATUS_LOG_FILTER<br>GET_LOCKS</code></td><td><code>GET_MIRRORS<br>GET_NEWEST_STATUS_LOG_ID<br>GET_OLDEST_STATUS_LOG_ID<br>GET_PROCEDURE_PRIVILEGES<br>GET_ROLE_GRANTS<br>GET_STATUS_LOG_FILTER<br>GET_STATUS_LOG<br>GET_THIS_MIRROR<br>SET_DATABASE_STATUS_LOG_FILTER<br>SET_PRIMARY_MIRROR<br>SET_STATUS_LOG_FILTER<br>SYNCH_MIRROR<br>VERIFY</code> </td></tr></table> <br> <h3><a name="DB_UTIL"></a>DB_UTIL: numeric, string, and date/time functions</h3><!--BNDX="DB_UTIL functions;SQL functions:DB_UTIL;math functions;string functions;date/time functions;utilities:DB_UTIL"--><p><code>DB_UTIL</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. They are a collection of SQL utility functions that perform numeric, string and date/time operations on data stored in database tables. </p><p><code>DB_UTIL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method. The description of each method includes a link to the exact implementation in <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_UTIL</code> provides the following methods</p><table border="0"><tr><td><code><br>ACOS<br>ASIN<br>ATAN<br>ATAN2<br>CEILING<br>COS<br>COT<br>DEGREES<br>EXP<br>FLOOR<br>LOG<br>LOG10<br>MOD<br>PI</code></td><td><br><code>POWER<br>RADIANS<br>RAND<br>ROUND<br>SIGN<br>SIN<br>SQRT<br>TAN<br>TRUNCATE<br>ASCII<br>TO_CHAR<br>DIFFERENCE<br>INSERT_STRING<br>LEFT_STRING</code></td><td><code><br>REPEAT<br>REPLACE<br>RIGHT<br>SOUNDEX<br>SPACE<br>DAYNAME<br>DAYOFWEEK<br>DAYOFYEAR<br>MONTHNAME<br>QUARTER<br>TIMESTAMPADD<br>TIMESTAMPDIFF<br>WEEK</code></td></tr></table> <br> <h3><a name="nullif"></a>NULLIF</h3><!--BNDX="NULLIF function;SQL functions:NULLIF;expressions:comparing;comparisons:expressions with NULLIF"--><p>The <code>NULLIF</code> function compares two expressions. It returns NULL if the expressions are equal. Otherwise, it returns the first expression. It is logically equivalent to the following <code>CASE</code> expression: <code>CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END</code><br><br>For more information, see <code>NULLIF</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="octet_length"></a>OCTET_LENGTH</h3><!--BNDX="OCTET_LENGTH function;SQL functions:OCTET_LENGTH;length of string, imput stream, or object"--><p>The <code>OCTET_LENGTH</code> function gives the length in bytes of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>OCTET_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="user_function"></a>USER</h3><!--BNDX="USER function;SQL functions:USER"--><p>The <code>USER</code> function returns the name of the current user; this function is the same as <code><a href="#current_user">CURRENT_USER</a></code>. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="new_sql"></a>New and updated SQL statements</h2><h3><a name="create_schema"></a>CREATE SCHEMA</h3><!--BNDX="CREATE SCHEMA statement;schemas:creating;SQL statements:CREATE SCHEMA"--><!--BNDX="statements, <em>see</em> SQL statements"--><p>The <code>CREATE SCHEMA</code> statement creates a name space for tables, views, and methods. You can use <code>CREATE SCHEMA</code> to create multiple objects in one SQL statement. For a discussion of how schemas work in JDataStore, see <code>CREATE SCHEMA</code> and <code>DROP SCHEMA</code>in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_schema"></a>DROP SCHEMA</h3><!--BNDX="DROP SCHEMA statement;schemas:dropping;SQL statements:DROP SCHEMA"--><p>The <code>DROP SCHEMA</code> statement deletes the specified schema. If the command is used without options, it is the same as specifying the <code>RESTRICT</code> option: the schema to be dropped must be empty. The command fails if the schema contains any objects. </p> <p class="bscan"><span class="bscan">Note: </span>The <code>DROP SCHEMA</code> command used with the <code>CASCADE</code> option is extremely powerful and should be used with caution. When this command is issued, it drops the schema and all of its objects and dependencies without any chance to change your mind. There is no undo.</p> <h3><a name="create_view"></a>CREATE VIEW</h3><!--BNDX="CREATE VIEW statement;SQL statements:CREATE VIEW;views:creating"--><p>The <code>CREATE VIEW</code> statement creates a derived table by selecting specified columns from existing tables. Views provide a way of accessing a consistent subcollection of the data stored in one or more tables. When the data in the underlying tables changes, the view reflects this change.</p>For more information, see <code>CREATE VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="alter_view"></a>ALTER VIEW</h3><!--BNDX="ALTER VIEW statement;SQL statements:ALTER VIEW;views:altering"--><p>The <code>ALTER VIEW</code> statement modifies a view without losing dependent views and existing <code>GRANT</code>s. This statement can be used to change the name of a view, the columns that comprise the view, and whether the view has the <code>WITH CHECK OPTION</code> constraint. For more information, see <code>ALTER VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_view"></a>DROP VIEW</h3><!--BNDX="DROP VIEW statement;SQL statements:DROP VIEW;views:dropping"--><p>The <code>DROP VIEW</code> statement drops the named view. By default, it fails if there are dependencies on the view. The <code>CASCADE</code> option drops the view and any dependent views. For more information, see <code>DROP VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_role"></a>CREATE ROLE</h3><!--BNDX="CREATE ROLE statement;SQL statements:CREATE ROLE;roles:creating;privileges:roles"--><p>The <code>CREATE ROLE</code> statement creates a named role. To complete this functionality, you must <code>GRANT</code> privileges to the role, and <code>GRANT</code> the role to one or more users. To make use of the privileges acquired in this fashion, the user issues a <code>SET ROLE</code> statement.</p><p>For more information, see <code>CREATE ROLE</code> and the <code>GRANT</code> statement in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="set_role"></a>SET ROLE</h3><!--BNDX="SET ROLE statement;SQL statements:SET ROLE;roles:activating;privileges:roles"--><p>The <code>SET ROLE</code> statement makes the named role active. The current user acquires all privileges assigned to that role. For more information, see <code>SET ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_role"></a>DROP ROLE</h3><!--BNDX="DROP ROLE statement;SQL statements:DROP ROLE;roles:dropping"--><p>The <code>DROP ROLE</code> statement drops the specified role. For more information, see <code>DROP ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_table"></a>CREATE TABLE</h3><!--BNDX="CREATE TABLE statement;JDataStore tables:creating;foreign keys;SQL statements:CREATE TABLE"--><!--BNDX="schemas:creating tables in;JDataStore tables:schemas"--><p>There are three new options for the <code>CREATE TABLE</code> statement:</p><ul><li>The table name now incldues a schema name.</li><li>You have the option of specifying a position for each column.</li><li>You can use the [NOT] RESOLVABLE option to track data changes for DataExpress.</li></ul><p>For more information, see <code>CREATE TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_table"></a>ALTER TABLE</h3><!--BNDX="ALTER TABLE statement;JDataStore tables:modifying;SQL statements:ALTER TABLE"--><p>There are several new options for the <code>ALTER TABLE</code> statement:</p><ul><li>You can rename the entire table; this is how you assign a table to a different schema.</li><li>You can make the table <code>RESOLVABLE</code> or <code>NOT RESOLVABLE</code>.</li><li>At the column level you can:<ul><li>Change the datatype of a column</li><li>Set whether a collumn is nullable</li><li>Rename a column</li><li>Change the position of a column within the table</li></ul></li></ul><p>For more information, see <code>ALTER TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_table"></a>DROP TABLE</h3><!--BNDX="DROP TABLE statement;SQL statements:DROP TABLE;JDataStore tables:deleting"--><p>The <code>DROP TABLE</code> statement deletes a table and its indexes from a JDataStore database. <code>DROP TABLE</code> has two new options: <code>RESTRICT</code> and <code>CASCADE</code>.</p> <h3><a name="create_java_class"></a>CREATE JAVA_CLASS</h3><!--BNDX="CREATE JAVA_CLASS statement;SQL statements:CREATE JAVA_CLASS;Java classes:creating;creating:java classes"--> <p>The <code>CREATE JAVA_CLASS</code> statement makes all public static methods of a Java class available to JDataStore SQL as stored procedures or UDFs. For more information, see <code>CREATE JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="drop_java_class"></a>DROP JAVA_CLASS</h3><!--BNDX="DROP JAVA_CLASS statement;SQL statements:DROP JAVA_CLASS;Java classes:dropping;dropping:java classes"--> <p>The <code>DROP JAVA_CLASS</code> statement drops a stored class, making it unavailable for use in JDataStore SQL. For more information, see <code>DROP JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="grant_statement"></a>GRANT</h3><!--BNDX="GRANT statement;SQL statements:GRANT;database privileges, granting;privileges:granting;roles:granting privileges to;roles:granting to users"--><p>The <code>GRANT</code> statement performs the following actions:</p><ul><li>It grants object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods to <code>PUBLIC</code>, users, or roles.</li><li>It grants database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—to users or roles.</li><li>It grants roles to users or roles.</li></ul>For more information, see <code>GRANT</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="revoke_statement"></a>REVOKE</h3><!--BNDX="REVOKE statement;SQL statements:REVOKE;database privileges, revoking;roles:revoking privileges"--><p>The <code>REVOKE</code> statement performs a number of actions:</p><ul><li>It revokes object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods from <code>PUBLIC</code>, users, or roles. It has <code>CASCADE</code> and <code>RESTRICT</code>,options.</li><li>It revokes database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—from users or roles.</li><li>It revokes roles from users or roles.</li><li>It revokes the <code>ADMIN</code> option from a role without revoking the role itself.</li><li>It revokes the <code>GRANT</code> option from a privilege without revoking the privilege itself.</li></ul><p>For more information, see <code>REVOKE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_user"></a>CREATE USER</h3><!--BNDX="CREATE USER statement;SQL statements:CREATE USER;users:adding with CREATE USER"--><p>The <code>CREATE USER</code> statement adds the named user and associated password to the database. The password is case sensitive, the user name is not. For more information, see <code>CREATE USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_user"></a>ALTER USER</h3><!--BNDX="ALTER USER statement;SQL statements:ALTER USER;users:editing with ALTER USER"--><p>The <code>ALTER USER</code> statement sets a new password for an existing user. For more information, see <code>ALTER USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_user"></a>DROP USER</h3><!--BNDX="DROP USER statement;SQL statements:DROP USER;users:removing with DROP USER"--><p>The <code>DROP USER</code> statement drops a user and all objects that the user owns. It has <code>RESTRICT</code> and <code>CASCADE</code> options. For more information, see <code>DROP USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="set_transaction"></a>SET TRANSACTION</h3><!--BNDX="SET TRANSACTION statement;SQL statements:SET TRANSACTION;transactions: setting; transaction isolation levels, overview;isolation levels:setting"--><p>The <code>SET TRANSACTION</code> statement sets the properties for the following transaction. You can use it to specify the isolation level and whether the transaction is read-write or read-only. For more information, see <code>SET TRANSACTION</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. See <a href="architecture.html#tx_management">"Transaction management"</a> in the "System Architecture" chapter for further discussion of JDataStore transaction management.</p><h3><a name="tinyint"></a>New data type: TINYINT</h3><p>JDataStore SQL now provides a one-byte integer data type, <code>TINYINT</code> (or <code>BYTE</code>). For more information, see "Datatypes" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="escape_functions"></a>JDBC escape functions</h3><!--BNDX="JDBC escape functions;SQL functions:JDBC escape functions;functions:JDBC escape functions"--><p>JDataStore now provides a greatly expanded list of JDBC escape functions. For a complete list, see "JDBC escape functions" the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="isql"></a>ISQL</h3><p>JDataStore's new ISQL can be run in the SQL tab of the Server Console. These commands can also be issued from any system command console.</p><p>For a discussion of JDataStore new ISQL and a list of commands, see <code>ISQL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="notes"></a>Product notes</h2><h3><a name="choose"></a>Choosing between JdsExplorer and the Server Console</h3><p>The Server Console is a graphical interface that is new in JDataStore 7. In it, you can perform some of the tasks that you previously performed in JdsExplorer. In addition, Server Console provides access to many new features.</p><p>From Server Console you can:</p><ul><li>Create and edit datasources, connect to local or remote databases, and view and manage connections. </li><li>View and manage database properties, and view database status logs, view table and row locks. and verify databases. You cannot create databases in Server Console.</li><li>Create and manage mirrors for incremental backup, auto failover, and load balancing.</li><li>Use the ISQL tab to execute all SQL and ISQL commands. There is a list of ISQL commands at the end of the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite>. JdsExplorer off an environment for executing SQL commands, but you cannot execute ISQL commands there.</li></ul><p>You need JdsExplorer if you want to:</p><ul><li>Perform user administration</li><li>Manage license keys</li><li>Work with and view table structure and content, including indexes.</li><li>Import tables from other databases and import text and images into a database</li><li>Upgrade, downgrade, copy, encrypt/decrypt or pack a database. Database verification can be performed from either JdsExplorer or Server Console.</li></ul><p>Most of the tasks listed for JdsExplorer can be performed in the Server Console using the ISQL window.</p><h3><a name="change_copy"></a>A change to the "Copy JDataStore" menu item</h3><p>JdsExplorer has a Copy JDataStore item on the Tools menu. Its function is different in JDataStore 7 then in earlier versions of the product. In previous versions of JDataStore, choosing Tools|Copy JDataStore brought up the Copy Streams dialog box, and made you select exactly which streams to copy. Now this menu item brings up a dialog in which you copy an entire database file.</p><p>There is a new item on the JDataStore Tools menu: Copy Into Existing JDataStore. This item permits you to copy into an existing, empty JDataStore, which allows you to downgrade or encrypt databases.</p><p>To copy individual tables between databases, use the Tools|Import chose in JdsExplorer.</p> <h2><a name="new_doc"></a>New and updated documentation</h2><h3><a name="new_chaps"></a>New chapters</h3><p>There are two new chapters in the <cite>JDataStore Developer's Guide</cite>. </p><ul><li>The "What's New" chapter lists the new features and provides links into those topics in the book.</li><li>The "JDataStore Server Console" chapter provides details about the new Server Console interface and the things you can do with it.</li></ul><h3><a name="exapnd_sql"></a>Expanded SQL Reference</h3><p>The JDataStore implementation of the SQL language has been greatly enriched, and the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite> has been expanded and reorganized.</p><h3><a name="escape"></a>JDBC escape syntax</h3><!--BNDX="JDBC escape sequences;JDataStore tables:string functions;JDataStore tables:JDBC escape sequences;literals in JDBC escape sequences"--><p>The JDBC escape syntax was not previously documented. It is now in the "JDBC escape syntax" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jdbc_resultset"></a>Stored procedures and JDBC ResultSets</h3><!--BNDX="JDBC result set;result set, JDBC;returning a JDBC result set"--><!--BNDX="JDBC DataSets;DataSets, returning"--><p>A Java stored procedure can produce a <code>ResultSet</code> on the client by returning either a <code>ResultSet</code> or a DataExpress <code>DataSet</code> from the Java implementation of the stored procedure. The <code>DataSet</code> is automatically converted to a <code>ResultSet</code> for the user of the stored procedure.</p><p>Documentation on the feature has been expanded in JDataStore 7. For more information, see "Stored procedures and JDBC ResultSets" in the "Stored Procedures and UDFs" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="start"></a>Getting started with JDataStore 7</h2><h3><a name="migration"></a>Migrating older databases to JDataStore 7</h3><p>The big issue in migrating older databases to JDataStore 7 is that JdataStore 7 has the concept of schemas, and older databases do not. In JDataStore 7, every table belongs to a schema: the schema name is part of the table name. In general, when a user creates an object such as a table or a view, that object belongs to the user's own schema. There are a number of issues regarding the use of schemas. It will be helpful to you to read <code>CREATE SCHEMA</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> to understand how JDataStore 7 uses schemas before proceeding with migration.</p><p>For additional detail on migrating older JDataStore databases to JDataStore 7, see "Migrating older databases to JDataStore 7" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jb_bes"></a><strong>Using JDataStore 7 with JBuilder and the Borland Enterprise Server</strong></h3><p>To make the latest version of JDataStore available to JBuilder and the Borland Enterprise Server (BES), you need to copy certain files form the JDataStore <em>lib</em> directory to the <em>lib</em> directory of the target product. The files are: <em>beandt.jar</em>, <em>dbtools.jar</em>, <em>dx.jar</em>, <em>jds.jar</em>, <em>jdsremote.jar</em>, and <em>jdsserver.jar</em></p><p>For more information, see "Using JDataStore with JBuilder and the Borland Enterprise server" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><p>Field test note: For the field test, copying these files may cause some menu problems in JBuilder. These problems go away when you remove the copied files. This defect will be fixed for the final release.</p><h2>Change listing for each point release.</h2><h3><a name="fixed_706">Bugs Fixed in 7.06</a></h3><ul><li>Mac installer has been replaced with an installer for intel Mac platform. PowerPC mac's are no longer supported.</li></ul><ul><li>Certain prepared queries with aggregators resulted in bad data.</li></ul><ul><li>Certain prepared queries with an IN operator resulted in a sporadic NullPointer exception. Safeguards have been added.</li><li>If a range is specified in the WHERE clause for an autoincrement column, the wrong rows might be returned. This is also true for certain primary key columns that implicitly are converted into auto increment columns.</li><li>JDataStore 7.006 has been certified for Microsoft Vista. We recommend that the developer edition of JDataStore be installed outside of the “Program Files” directory. The JDataStore .exe launchers depend on config files that are located in the same directory as the launcher.exe. If the product is installed in the “Program Files” directory and Vista UAC is enabled, the changes to the config files will only take affect for the user that makes the modifications. Note that this is mostly of concern to developers or server side installations that use one of the exe launchers. These are the exe Launchers installed by the developer edition of JDataStore: JdsServer*.exe, isql.exe, JdsExplorer*.exe, and ServerConsole*.exe. Note that there are no issues for installing JDataStore jar files in the “Program Files” directory.</li><li>Data corruption from sql update statements under high concurrency environments has been fixed.<li></li>Thread deadlock in JdbcConnectionPool shutdown method that occurs when another thread is also returning a connection to the pool by calling java.sql.Connection.close method has been fixed.</li><li>ArrayIndexOutOfBoundsException that occurs for descending sort operations on String columns</li><li>Prepared statement with grouping criteria may produce incorrect results the second time it is executed when other statements that use the same table are prepared and executed.</li><li>Joins with range selection criteria for more than one table on columns with the same ordinal position can encounter value access errors indicating a type mismatch.</li><li>DB_ADMIN.GET_CONNECTIONS() built in stored procedure will now include local connections in addition to remote connections. This includes connections open with the DataStoreConnection and DataStore components. Connections with a "USER" column that starts with "sys." and connections that have a "REMARKS" column value of "Opener" are internal connections that do not keep a database from shutting down.</li> <h3><a name="fixed_705">Bugs Fixed in 7.05</a></h3><ul><li>An UPDATE query which uses an aggregation of a subquery with an outer reference to set a column value could cause a NullPointerException.</li><li>DatabaseMetaData.getIndexInfo() returned wrong information about auto increment columns.</li><li>A combination of a 1-1 query of 2 tables with single integer column primary keys and an IN operator in the WHERE clause could cause an Exception.</li><li>Creating a table with a single integer column primary key and a different column as an auto increment column, will cause the auto increment column to not function.</li><li>Applications that close connections without closing open statements will incur a memory leak if the statements had executed queries that return ResultSets.</li><li>SQL queries with an “in clause” selection criteria that references an indexed column may not return all rows that satisfy the in clause selection criteria.</li><li>Table open and close operations can fail if several connections are rapidly opening and closing connections. This can also cause connection close operations to fail resulting in "lingering" connections in the DataStoreServer.</li><li>Statement caching provided by the connection pool does not properly cache or close statements. Because resources and ResultSets are not closed until these unclosed statements are finalized, this can lead to out of memory conditions and large temporary database file sizes.</li><li>For encrypted databases, the crash recovery system can encrypt modified blocks of the user table. This is a mistake because the user table is the one table that cannot be encrypted in an encrypted database. Note that this will only occur if some change is made to the user table since the last time the database was opened. This problem can prevent the database from being opened or cause the user table to appear corrupt when database verification is performed. We are working on a repair method for applications that have encountered this problem.</li><li>Support for opening encrypted databases that have part or all of the user table encrypted by the defect described above. If the user table record for the user connecting is encrypted, the database cannot be opened. In this case there is a new connection property called "priorFileName" that can be used to provide the name of a prior version of the encrypted database that can still be opened. This can be specified as an extended JDBC property for JDBC connections. There is also a DataStoreConnection.setPriorFileName as well. Note that the prior database will only be used to unencrypt the user table that is not supposed to be encrypted in the first place. If the user logging in does not have startup rights in both the prior and current database, the prior database will not be used for the open operation. Once the database affected by this defect has been opened, it should be copied or packed into a new database file.</li></ul> <h3><a name="fixed_704">Bugs Fixed in 7.04</a></h3><ul><li>When "Tools | Encrypt JDataStore" or "Tools | Copy JDataStore" is selected from JdsExplorer, the resulting database has multiple entries for the SYSDBA user. This problem has been fixed.</li><li>When combining an "order by" and an "in" and a sub select on a large set of records, it may result in an incorrect record count.</li></ul> <h3><a name="fixed_703">Bugs Fixed in 7.03</a></h3><h4>Support for Hibernate</h4><ul><li>Hibernate's automated test suites completed. Hibernate dialect class provided in samples directory.</li></ul><h4>General defect corrections and improvements</h4><ul><li>ADMINISTRATOR is now a non reserved keyword in SQL. (It used to be a reserved keyword.)</li><li>Corrected defect in remote driver where retrieving longer string or blob values sometimes caused the driver to hang. </li><li>Database check point events are now logged in the *STATUS * log files. These messages provide "remarks" on what is keeping a log file from being dropped. This can be useful when trying to diagnose why log files are not being automatically dropped. </li><li>New ExtendedProperties.REMARKS property. This can be set to an informative string. This is displayed in many of the contexts in which user name is displayed. Many applications use the same user for many connections. The remarks property makes it easier to distinguish connections that use the same user name. Remarks is displayed for lock error reporting, DB_ADMIN.GET_CONNECTIONS() builtin stored procedure and the connections node of the ServerConsole. </li></ul><h4>SMP support</h4><ul><li>Completion of all automated stress tests on dual processor Windows XP and Redhat Enterprise Linux 3. </li></ul><h4>High availability corrected defects and improvements</h4><ul><li>General stability improvements. </li><li>Improved performance for mirror synchronization. </li><li>Eliminated problems where log files would never drop for databases with mirrors in certain situations. </li><li>Mirrors with the INSTANT_SYNCH or AUTO_FAIL_OVER property set will automatically have a mirror schedule item added to the SYS.MIRROR_SCHEDULE table. This mirror schedule item is added when the mirror is created or when the INSTANT_SYNCH or AUTO_FAIL_OVER property is altered for a mirror that does not already have a mirror schedule item. This default mirror schedule item will synchronize the mirror every 10 seconds. This mirror schedule item can be dropped or altered after the mirror is created if so desired. However, it is probably best to keep a mirror schedule item for each mirror so that the read only mirror database is kept up to date with the primary mirror. When INSTANT_SYNCH or the AUTO_FAIL_OVER property is set for a read only mirror its log records are constantly kept in synch with the primary mirror. However, these log records are not replayed against the read only mirror database until a synch operation is performed. The mirror schedule item will synch the mirror on a regular basis keeping the state of the read only mirror database very close or equal to the state of the primary mirror. Two key benefits of having the readonly mirror databases up to date with the primary mirror are: 1) Fail over (manual or automatic) is much faster because little or no log records need to be replayed before the fail over operation. 2) Readonly mirror databases will reflect a more recent state of the database. This will be important for applications that off load readonly queries from the primary mirror to readonly mirrors. </li><li>ISQL show ddl command now outputs the sql call statements to recreate any mirrors configured for the database. This is useful to see how mirrors are can be created from executing a sql script. </li><li>The last known replay column for the mirrors table and mirror status table in the ServerConsole now displays these values in hex. The high 32 bits are the log file and the low 32 bits are the offset into the log files. These values determine when log files can be automatically dropped. For example a primary mirror cannot drop a log if a read only mirror has not replayed the contents of that log file. So if the last known replay for a read only mirror as a low log file for its last replay column, this will keep this log file and all log files greater than this log file from being dropped. </li></ul> <h3><a name="fixed_702">Bugs Fixed in 7.02</a></h3><ul><li>There have been many significant improvements in High availability Mirrors as well as Read-Only Transactions. </li><li>Mirroring support now drops unneeded log files when it should. </li><li>Cannot use export or show ddl command when a database has multiple schemas because there are no schema creation statements emitted. Insert statements for export also need to prefix table names with schema name. This problem has been fixed. </li><li>DatabaseMetadata now show a foreign keys for other schemas when logging in as SYSDBA. </li><li>ADMIN is still a keyword, but not a reserved one. </li><li>When two separate threads are allocating a new log file at the same time, the potential for a deadlock no longer occurs. </li><li>SHOW DDL did not generate "CREATE SCHEMA" statements. This is needed if the output is to be executed against another database. </li> <li>Foreign keys are now reported in show ddl for non-default schema when logged in as sysdba (administrator). </li><li>Show ddl command now works for a table with an autoincrement column. </li><li>An exception is reported when there are two tables with foreign keys that reference each other, and both tables are being updated by separate transactions a lock timeout error can occur. This has been fixed. </li><li>Wrong result from running join query has been fixed. </li></ul> <h3><a name="fixed_701">Bugs Fixed in 7.01</a></h3><ul><li>Modify output of date and time to include at least 2 digits for day, month, minute, second, hours. </li><li>Remote JDBC driver improved server exception handling. </li><li>A prepared query with a parameterized LIKE operator in the where clause e.g. "SELECT * FROM PERSON WHERE LASTNAME LIKE ?"was mistakenly executed with the parameter given first time the query was executed; thus subsequent executions would receive wrong results. This problem has been fixed. </li><li>A SQL query which uses an auto-increment field for a lookup or join may in certain circumstances yield the wrong result. This problem has been fixed. </li><li>Tables with a column named INTERNALROW, could not be exported using ISQL. This problem has been fixed. </li><li>The data presented in the ServerConsole and the SQL tab in JdsExplorer for a query like: "SELECT * FROM MY_VIEW" could not be edited even if the view was updateable. This problem has been fixed. </li><li>TxException LOCK_TIMEOUT errors fixed for situations where table lock escalation is triggered to max row locks exceeded. </li><li>Problem when value from source cursor had a maxInline setting that was larger than the destination cursor. Cursor now can convert inline into blob if necessary. </li><li>Drop column no longer fails to have any affect if another connection has a prepared statement that references the same table. </li><li>The command SHOW TABLE in ISQL required an explicit schema name. This problem has been fixed. </li><li>Cannot drop primary mirror. Problem is now fixed. </li> <li>ResultSetMetaData now returns the correct column count when an updateable ResultSet is used. </li><li>Column from Primary keys were sometimes reported to be nullable through DatabaseMetadata.getColumns().This problem has been fixed. </li><li>If 2 timestamp values are given as 2 literals the first value is stored for both values. This problem has been fixed. </li><li>The Date and Timestamp literal JDBC escape formats were incorrectly documented. This problem has been fixed. </li></ul> http://cc.embarcadero.com/Item/25370 2008-05-13T22:20:45 2008-05-13T22:20:45 http://cc.embarcadero.com/Item/25370 <h1 align="center"><a name="_top_"></a>JDataStore 7.06 (build 7.006.039) for Windows<br>Release Notes</h1><p>These Release Notes provide a brief description of each new feature in JDataStore 7.The <cite>JDataStore Developer's Guide</cite> includes a "What's New" chapter that provideslinks to the documentation for each new feature within the Developer's Guide.</p><p><strong>Bug fix list</strong></p><ul><li>To see bugs fixed in JDataStore 7.06 click <a href="#fixed_706">here</a></li><li>To see bugs fixed in JDataStore 7.05 click <a href="#fixed_705">here</a></li><li>To see bugs fixed in JDataStore 7.04 click <a href="#fixed_704">here</a></li><li>To see bugs fixed in JDataStore 7.03 click <a href="#fixed_703">here</a></li><li>To see bugs fixed in JDataStore 7.02 click <a href="#fixed_702">here</a></li><li>To see bugs fixed in JDataStore 7.01 click <a href="#fixed_701">here</a></li></ul><p><strong>New Features</strong></p><ul><li><a href="#failsafe">The JDataStore High Availability Server: incremental backup, automatic failover</a></li><li>The new <a href="#console">Server Console</a> graphical interface</li></ul><p><strong>New SQL functions</strong></p><ul><li><a href="#bit_length"><code>BIT_LENGTH</code></a></li><li><a href="#case_function"><code>CASE</code></a></li><li><a href="#coalesce"><code>COALESCE</code></a></li><li><a href="#current_role"><code>CURRENT_ROLE</code></a></li><li><a href="#current_user"><code>CURRENT_USER</code></a></li><li><a href="#db_admin"><code>DB_ADMIN</code></a></li><li><a href="#DB_UTIL"><code>DB_UTIL</code></a></li><li><a href="#nullif"><code>NULLIF</code></a></li><li><a href="#octet_length"><code>OCTET_LENGTH</code></a></li><li><a href="#user_function"><code>USER</code></a></ul><p><strong>New and updated SQL statements</strong></p><ul><li><a href="#create_schema"><code>CREATE SCHEMA</code></a>, <a href="#drop_schema"><code>DROP SCHEMA</code></a></li><li><a href="#create_view"><code>CREATE VIEW</code></a>, <a href="#alter_view"><code>ALTER VIEW</code></a>, <a href="#drop_view"><code>DROP VIEW</code></a></li><li><a href="#create_role"><code>CREATE ROLE</code></a>, <a href="#set_role"><code>SET ROLE</code></a>, <a href="#drop_role"><code>DROP ROLE</code></a></li><li>New <code><a href="#create_table">CREATE TABLE</a></code> options</li><li>New <code><a href="#alter_table">ALTER TABLE</a></code> options</li><li>New <code><a href="#drop_table">DROP TABLE</a></code> options: <code>CASCADE</code> and <code>RESTRICT</code></li><li><a href="#create_java_class"><code>CREATE JAVA_CLASS</code></a>, <code><a href="#drop_java_class">DROP JAVA_CLASS</a></code></li></ul><p><strong>Security management</strong></p><ul><li><code><a href="#grant_statement">GRANT</a></code> and <code><a href="#revoke_statement">REVOKE</a></code></li><li><code><a href="#create_user">CREATE USER</a></code>, <code><a href="#alter_user">ALTER USER</a></code>, <code><a href="#drop_user">DROP USER</a></code></li></ul><p><strong>Transaction management</strong></p><ul><li><code><a href="#set_transaction">SET TRANSACTION</a></code></ul><p><strong>Other new SQL</strong></p><ul><li><a href="#keywords">New keywords</a></li><li>New data type: <a href="#tinyint"><code>TINYINT</code></a></li><li>Many new <a href="#escape_functions">JDBC escape functions</a></li><li><a href="#isql">ISQL cross-platform SQL command-line utility</a></li></ul><p><strong>Product notes</strong></p><ul><li><a href="#choose">Choosing between Server Console and JdsExplorer</a></li><li><a href="#change_copy">A change to the "Copy JDataStore" menu item</a></li></ul><p><strong>New and updated documentation</strong></p><ul><li><a href="#new_chaps">New chapters</a></li><li><a href="#escape">Escape syntax for calling stored procedures</a> is now documented.</li><li>Updated documentation on <a href="#jdbc_resultset">returning JDBC ResultSets</a></li></ul><p><strong>Getting started with JDataStore 7</strong></p><ul><li><a href="#migration">Migrating older databases to JDataStore 7</a></li><li><a href="#jb_bes">Using JDataStore 7 with JBuilder and the Borland Enterprise server</a></li></ul><!-- <p><a href="#bugs">Defects fixed in JDataStore 7</a></p> --><!-- <h2><a name="features"></a>New features</h2> --><h2><a name="features"></a>New features</h2><h3><a name="failsafe"></a>The JDataStore High Availability Server</h3><p>JDataStore 7 provides tools for creating automatic or manual incremental backups and for creating automatic failover to a mirror of the original database in case of failure. In addition, there are tools for viewing and managing connections on a remote server, for managing datasources and connections graphically or with the new ISQL feature, for viewing database status logs and transactions logs, for viewing logs, and for verifying databases.</p><p>The "High Availability Server" topic in the "Architecture" chapter of the <cite>JDataStore Developer's Guide</cite> discusses the architecture of JDataStore's new failsafe server and its associated mirroring functionality. This section is well worth reading, because it will help you make the most of this new offerings. </p><p>For a description of how to use JDataStore's new Server Console to access this new functionality, see the new "JDataStore Server Console" chapter in the <cite>JDataStore Developer's Guide</cite>. </p> <h3><a name="console"></a>The new Server Console graphical interface</h3><p>There is a whole new graphical interface in JDataStore 7. The Server Console performs many server administration tasks, including several that are new in JDataStore 7, such as automatic failover and incremental backup.</p><p>Here is an overview of what you can do with the Server Console. The items in the following list are topics in the "JDataStore Server Console" chapter of the <cite>JDataStore Developer's Guide</cite> for details.</p><ul><li><strong>Overview</strong> Get a quick overview of what you can do with Server Console</li><li><strong>About datasources</strong> If you're not familiar with how JDataStore uses dataasources to connect to databases, this is the place to find out.</li><li><strong>What you see and what you get</strong> Get familiar with the new Server Console interface.</li><li><strong>Starting/shutting down the server</strong> You can use Server Console to start and stop the local server.</li><li><strong>Connection settings</strong> A detailed description of how to create, modify, and delete datasources, and how to connect to and disconnect from them.</li><li><strong>Creating and managing datasources</strong> Create, rename, and modify datasources, connect to them, and disconnect from them.</li><li><strong>Verifying a database</strong> Server Console makes it easier than ever.</li><li><strong>Managing connections</strong> View and optionaly terminate both local and remote datasources.</li><li><strong>Managing database properties</strong> See an editable grid of database properties for both local and remote connections.</li><li><strong>Viewing table and row locks</strong> Server Console makes it easy to see what's happening with locks on both the local and remote server.</li><li><strong>Viewing the database status log file</strong> You exactly what's been going on with a server by viewing its server status file.</li><li><strong>Failover</strong> and <strong>incremental backup</strong> Use mirrors to protect against failures and to incrementally backup your data on a schedule of your choosing. Using Server Console, you can add </li><li><strong>Interactive SQL</strong> A special SQL pane lets you run SQL or SQL scripts against connected datasources.</li></ul><p><strong>What happened to the old JdsServer graphical interface?</strong> It's still there, but it has been replaced by the new Server Console. You can still start the JDataStore server as an application by running the <code>JdsServer</code> executable. However, it is now set to run without the GUI. If you really need that deprecated interface back, you can invoke the GUI by executing the following command:</p><table class="pre"><tr><td><pre>jdsserver -ui [windows|motif|metal|none][other parameters]</pre></td></tr></table><p>Choose the interface that is appropriate for your platform. For more about starting the JDataStore server, see "Launching JdsServer" in the "JDataStore Administration" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="keywords"></a>New keywords</h3><p>The asterisk following a keyword indicates that the keyword is <em>reserved</em>. Reserved keywords can be used as SQL identifiers only if they are enclosed in double quotation marks. When quoted in this fashion, they are case sensitive. The words that have no asterisk are <em>nonreserved</em> keywords. They can be used with or without double quotes and are case insensitive when note in quotes.</p><p>For a complete list of keywords, see <strong>Keywords</strong> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><table border="0"><tr><td>ADMIN*<br>ADMINISTRATOR*<br>AUTHORIZATION*<br>BIT_LENGTH*<br>COALESCE*<br>CURRENT_ROLE*<br>CURRENT_USER*<br>EXECUTE*<br>GRANT*<br>ISOLATION*<br></td><td>LEVEL*<br>NONE*<br>NULLIF*<br>OCTET_LENGTH*<br>ONLY*<br>OPTION*<br>PRIVILEGES*<br>PUBLIC*<br>READ<br>RENAME*<br></td><td>RESOLVABLE*<br>REVOKE*<br>ROLE<br>SCHEMA*<br>STARTUP*<br>TO*<br>TRANSACTION*<br>VIEW*<br>WITH*<br>WRITE<br></td></tr></table> <h2><a name="new_funcs"></a>New SQL functions</h2><h3><a name="bit_length"></a>BIT_LENGTH</h3><p>The <code>BIT_LENGTH</code> function gives the length in bits of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>BIT_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="case_function"></a>CASE</h3><!--BNDX="CASE function;SQL functions:CASE"--><p>The <code>CASE</code> function returns a conditional value. For more information, see <code>CASE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="coalesce"></a>COALESCE</h3><!--BNDX="COALESCE function;SQL functions:COALESCE;non-NULL values, returning"--><p>The <code>COALESCE</code> function returns the first non-NULL value from the expression list. For more information, see <code>COALESCE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="current_role">CURRENT_ROLE</a></h3><!--BNDX="CURRENT_ROLE function;SQL functions:CURRENT_ROLE;roles"--><p>The <code>CURRENT_ROLE</code> function returns the current role, or NULL if no role has been set using the <code>SET ROLE</code> statement. For more information, see <code>CURRENT_ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. </p><h3><a name="current_user"></a>CURRENT_USER</h3><!--BNDX="CURRENT_USER function;SQL functions:CURRENT_USER"--><p>The <code>CURRENT_USER</code> function returns the name of the current user. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="db_admin"></a>DB_ADMIN: administration functions</h3><!--BNDX="DB_ADMIN function;SQL functions:DB_ADMIN"--><p><code>DB_ADMIN</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. Use <code>DB_ADMIN</code> for various database administration tasks such as automatic failover, incremental backup, creating and managing datasources, viewing and managing connections, verifying tables, and displaying database privileges and properties, locks, status logs, procedure privileges, and roles granted.</p><p><code>DB_ADMIN</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method, implemented as a SQL function. The description of each method includes a link to the exact implementation and <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_ADMIN</code> provides the following methods:</p><table border="0" cols="3"><tr><td><code>ALTER_DATABASE<br>ALTER_MIRROR<br>ALTER_MIRROR_SCHEDULE<br>CLOSE_CONNECTION<br>CREATE_MIRROR<br>CREATE_MIRROR_SCHEDULE<br>DROP_MIRROR<br>DROP_MIRROR_SCHEDULE<br>GET_CONNECTIONS<br>GET_DATABASE_PRIVILEGES<br>GET_DATABASE_PROPS<br>GET_DATABASE_STATUS_LOG_FILTER<br>GET_LOCKS</code></td><td><code>GET_MIRRORS<br>GET_NEWEST_STATUS_LOG_ID<br>GET_OLDEST_STATUS_LOG_ID<br>GET_PROCEDURE_PRIVILEGES<br>GET_ROLE_GRANTS<br>GET_STATUS_LOG_FILTER<br>GET_STATUS_LOG<br>GET_THIS_MIRROR<br>SET_DATABASE_STATUS_LOG_FILTER<br>SET_PRIMARY_MIRROR<br>SET_STATUS_LOG_FILTER<br>SYNCH_MIRROR<br>VERIFY</code> </td></tr></table> <br> <h3><a name="DB_UTIL"></a>DB_UTIL: numeric, string, and date/time functions</h3><!--BNDX="DB_UTIL functions;SQL functions:DB_UTIL;math functions;string functions;date/time functions;utilities:DB_UTIL"--><p><code>DB_UTIL</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. They are a collection of SQL utility functions that perform numeric, string and date/time operations on data stored in database tables. </p><p><code>DB_UTIL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method. The description of each method includes a link to the exact implementation in <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_UTIL</code> provides the following methods</p><table border="0"><tr><td><code><br>ACOS<br>ASIN<br>ATAN<br>ATAN2<br>CEILING<br>COS<br>COT<br>DEGREES<br>EXP<br>FLOOR<br>LOG<br>LOG10<br>MOD<br>PI</code></td><td><br><code>POWER<br>RADIANS<br>RAND<br>ROUND<br>SIGN<br>SIN<br>SQRT<br>TAN<br>TRUNCATE<br>ASCII<br>TO_CHAR<br>DIFFERENCE<br>INSERT_STRING<br>LEFT_STRING</code></td><td><code><br>REPEAT<br>REPLACE<br>RIGHT<br>SOUNDEX<br>SPACE<br>DAYNAME<br>DAYOFWEEK<br>DAYOFYEAR<br>MONTHNAME<br>QUARTER<br>TIMESTAMPADD<br>TIMESTAMPDIFF<br>WEEK</code></td></tr></table> <br> <h3><a name="nullif"></a>NULLIF</h3><!--BNDX="NULLIF function;SQL functions:NULLIF;expressions:comparing;comparisons:expressions with NULLIF"--><p>The <code>NULLIF</code> function compares two expressions. It returns NULL if the expressions are equal. Otherwise, it returns the first expression. It is logically equivalent to the following <code>CASE</code> expression: <code>CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END</code><br><br>For more information, see <code>NULLIF</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="octet_length"></a>OCTET_LENGTH</h3><!--BNDX="OCTET_LENGTH function;SQL functions:OCTET_LENGTH;length of string, imput stream, or object"--><p>The <code>OCTET_LENGTH</code> function gives the length in bytes of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>OCTET_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="user_function"></a>USER</h3><!--BNDX="USER function;SQL functions:USER"--><p>The <code>USER</code> function returns the name of the current user; this function is the same as <code><a href="#current_user">CURRENT_USER</a></code>. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="new_sql"></a>New and updated SQL statements</h2><h3><a name="create_schema"></a>CREATE SCHEMA</h3><!--BNDX="CREATE SCHEMA statement;schemas:creating;SQL statements:CREATE SCHEMA"--><!--BNDX="statements, <em>see</em> SQL statements"--><p>The <code>CREATE SCHEMA</code> statement creates a name space for tables, views, and methods. You can use <code>CREATE SCHEMA</code> to create multiple objects in one SQL statement. For a discussion of how schemas work in JDataStore, see <code>CREATE SCHEMA</code> and <code>DROP SCHEMA</code>in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_schema"></a>DROP SCHEMA</h3><!--BNDX="DROP SCHEMA statement;schemas:dropping;SQL statements:DROP SCHEMA"--><p>The <code>DROP SCHEMA</code> statement deletes the specified schema. If the command is used without options, it is the same as specifying the <code>RESTRICT</code> option: the schema to be dropped must be empty. The command fails if the schema contains any objects. </p> <p class="bscan"><span class="bscan">Note: </span>The <code>DROP SCHEMA</code> command used with the <code>CASCADE</code> option is extremely powerful and should be used with caution. When this command is issued, it drops the schema and all of its objects and dependencies without any chance to change your mind. There is no undo.</p> <h3><a name="create_view"></a>CREATE VIEW</h3><!--BNDX="CREATE VIEW statement;SQL statements:CREATE VIEW;views:creating"--><p>The <code>CREATE VIEW</code> statement creates a derived table by selecting specified columns from existing tables. Views provide a way of accessing a consistent subcollection of the data stored in one or more tables. When the data in the underlying tables changes, the view reflects this change.</p>For more information, see <code>CREATE VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="alter_view"></a>ALTER VIEW</h3><!--BNDX="ALTER VIEW statement;SQL statements:ALTER VIEW;views:altering"--><p>The <code>ALTER VIEW</code> statement modifies a view without losing dependent views and existing <code>GRANT</code>s. This statement can be used to change the name of a view, the columns that comprise the view, and whether the view has the <code>WITH CHECK OPTION</code> constraint. For more information, see <code>ALTER VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_view"></a>DROP VIEW</h3><!--BNDX="DROP VIEW statement;SQL statements:DROP VIEW;views:dropping"--><p>The <code>DROP VIEW</code> statement drops the named view. By default, it fails if there are dependencies on the view. The <code>CASCADE</code> option drops the view and any dependent views. For more information, see <code>DROP VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_role"></a>CREATE ROLE</h3><!--BNDX="CREATE ROLE statement;SQL statements:CREATE ROLE;roles:creating;privileges:roles"--><p>The <code>CREATE ROLE</code> statement creates a named role. To complete this functionality, you must <code>GRANT</code> privileges to the role, and <code>GRANT</code> the role to one or more users. To make use of the privileges acquired in this fashion, the user issues a <code>SET ROLE</code> statement.</p><p>For more information, see <code>CREATE ROLE</code> and the <code>GRANT</code> statement in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="set_role"></a>SET ROLE</h3><!--BNDX="SET ROLE statement;SQL statements:SET ROLE;roles:activating;privileges:roles"--><p>The <code>SET ROLE</code> statement makes the named role active. The current user acquires all privileges assigned to that role. For more information, see <code>SET ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_role"></a>DROP ROLE</h3><!--BNDX="DROP ROLE statement;SQL statements:DROP ROLE;roles:dropping"--><p>The <code>DROP ROLE</code> statement drops the specified role. For more information, see <code>DROP ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_table"></a>CREATE TABLE</h3><!--BNDX="CREATE TABLE statement;JDataStore tables:creating;foreign keys;SQL statements:CREATE TABLE"--><!--BNDX="schemas:creating tables in;JDataStore tables:schemas"--><p>There are three new options for the <code>CREATE TABLE</code> statement:</p><ul><li>The table name now incldues a schema name.</li><li>You have the option of specifying a position for each column.</li><li>You can use the [NOT] RESOLVABLE option to track data changes for DataExpress.</li></ul><p>For more information, see <code>CREATE TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_table"></a>ALTER TABLE</h3><!--BNDX="ALTER TABLE statement;JDataStore tables:modifying;SQL statements:ALTER TABLE"--><p>There are several new options for the <code>ALTER TABLE</code> statement:</p><ul><li>You can rename the entire table; this is how you assign a table to a different schema.</li><li>You can make the table <code>RESOLVABLE</code> or <code>NOT RESOLVABLE</code>.</li><li>At the column level you can:<ul><li>Change the datatype of a column</li><li>Set whether a collumn is nullable</li><li>Rename a column</li><li>Change the position of a column within the table</li></ul></li></ul><p>For more information, see <code>ALTER TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_table"></a>DROP TABLE</h3><!--BNDX="DROP TABLE statement;SQL statements:DROP TABLE;JDataStore tables:deleting"--><p>The <code>DROP TABLE</code> statement deletes a table and its indexes from a JDataStore database. <code>DROP TABLE</code> has two new options: <code>RESTRICT</code> and <code>CASCADE</code>.</p> <h3><a name="create_java_class"></a>CREATE JAVA_CLASS</h3><!--BNDX="CREATE JAVA_CLASS statement;SQL statements:CREATE JAVA_CLASS;Java classes:creating;creating:java classes"--> <p>The <code>CREATE JAVA_CLASS</code> statement makes all public static methods of a Java class available to JDataStore SQL as stored procedures or UDFs. For more information, see <code>CREATE JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="drop_java_class"></a>DROP JAVA_CLASS</h3><!--BNDX="DROP JAVA_CLASS statement;SQL statements:DROP JAVA_CLASS;Java classes:dropping;dropping:java classes"--> <p>The <code>DROP JAVA_CLASS</code> statement drops a stored class, making it unavailable for use in JDataStore SQL. For more information, see <code>DROP JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="grant_statement"></a>GRANT</h3><!--BNDX="GRANT statement;SQL statements:GRANT;database privileges, granting;privileges:granting;roles:granting privileges to;roles:granting to users"--><p>The <code>GRANT</code> statement performs the following actions:</p><ul><li>It grants object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods to <code>PUBLIC</code>, users, or roles.</li><li>It grants database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—to users or roles.</li><li>It grants roles to users or roles.</li></ul>For more information, see <code>GRANT</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="revoke_statement"></a>REVOKE</h3><!--BNDX="REVOKE statement;SQL statements:REVOKE;database privileges, revoking;roles:revoking privileges"--><p>The <code>REVOKE</code> statement performs a number of actions:</p><ul><li>It revokes object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods from <code>PUBLIC</code>, users, or roles. It has <code>CASCADE</code> and <code>RESTRICT</code>,options.</li><li>It revokes database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—from users or roles.</li><li>It revokes roles from users or roles.</li><li>It revokes the <code>ADMIN</code> option from a role without revoking the role itself.</li><li>It revokes the <code>GRANT</code> option from a privilege without revoking the privilege itself.</li></ul><p>For more information, see <code>REVOKE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_user"></a>CREATE USER</h3><!--BNDX="CREATE USER statement;SQL statements:CREATE USER;users:adding with CREATE USER"--><p>The <code>CREATE USER</code> statement adds the named user and associated password to the database. The password is case sensitive, the user name is not. For more information, see <code>CREATE USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_user"></a>ALTER USER</h3><!--BNDX="ALTER USER statement;SQL statements:ALTER USER;users:editing with ALTER USER"--><p>The <code>ALTER USER</code> statement sets a new password for an existing user. For more information, see <code>ALTER USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_user"></a>DROP USER</h3><!--BNDX="DROP USER statement;SQL statements:DROP USER;users:removing with DROP USER"--><p>The <code>DROP USER</code> statement drops a user and all objects that the user owns. It has <code>RESTRICT</code> and <code>CASCADE</code> options. For more information, see <code>DROP USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="set_transaction"></a>SET TRANSACTION</h3><!--BNDX="SET TRANSACTION statement;SQL statements:SET TRANSACTION;transactions: setting; transaction isolation levels, overview;isolation levels:setting"--><p>The <code>SET TRANSACTION</code> statement sets the properties for the following transaction. You can use it to specify the isolation level and whether the transaction is read-write or read-only. For more information, see <code>SET TRANSACTION</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. See <a href="architecture.html#tx_management">"Transaction management"</a> in the "System Architecture" chapter for further discussion of JDataStore transaction management.</p><h3><a name="tinyint"></a>New data type: TINYINT</h3><p>JDataStore SQL now provides a one-byte integer data type, <code>TINYINT</code> (or <code>BYTE</code>). For more information, see "Datatypes" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="escape_functions"></a>JDBC escape functions</h3><!--BNDX="JDBC escape functions;SQL functions:JDBC escape functions;functions:JDBC escape functions"--><p>JDataStore now provides a greatly expanded list of JDBC escape functions. For a complete list, see "JDBC escape functions" the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="isql"></a>ISQL</h3><p>JDataStore's new ISQL can be run in the SQL tab of the Server Console. These commands can also be issued from any system command console.</p><p>For a discussion of JDataStore new ISQL and a list of commands, see <code>ISQL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="notes"></a>Product notes</h2><h3><a name="choose"></a>Choosing between JdsExplorer and the Server Console</h3><p>The Server Console is a graphical interface that is new in JDataStore 7. In it, you can perform some of the tasks that you previously performed in JdsExplorer. In addition, Server Console provides access to many new features.</p><p>From Server Console you can:</p><ul><li>Create and edit datasources, connect to local or remote databases, and view and manage connections. </li><li>View and manage database properties, and view database status logs, view table and row locks. and verify databases. You cannot create databases in Server Console.</li><li>Create and manage mirrors for incremental backup, auto failover, and load balancing.</li><li>Use the ISQL tab to execute all SQL and ISQL commands. There is a list of ISQL commands at the end of the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite>. JdsExplorer off an environment for executing SQL commands, but you cannot execute ISQL commands there.</li></ul><p>You need JdsExplorer if you want to:</p><ul><li>Perform user administration</li><li>Manage license keys</li><li>Work with and view table structure and content, including indexes.</li><li>Import tables from other databases and import text and images into a database</li><li>Upgrade, downgrade, copy, encrypt/decrypt or pack a database. Database verification can be performed from either JdsExplorer or Server Console.</li></ul><p>Most of the tasks listed for JdsExplorer can be performed in the Server Console using the ISQL window.</p><h3><a name="change_copy"></a>A change to the "Copy JDataStore" menu item</h3><p>JdsExplorer has a Copy JDataStore item on the Tools menu. Its function is different in JDataStore 7 then in earlier versions of the product. In previous versions of JDataStore, choosing Tools|Copy JDataStore brought up the Copy Streams dialog box, and made you select exactly which streams to copy. Now this menu item brings up a dialog in which you copy an entire database file.</p><p>There is a new item on the JDataStore Tools menu: Copy Into Existing JDataStore. This item permits you to copy into an existing, empty JDataStore, which allows you to downgrade or encrypt databases.</p><p>To copy individual tables between databases, use the Tools|Import chose in JdsExplorer.</p> <h2><a name="new_doc"></a>New and updated documentation</h2><h3><a name="new_chaps"></a>New chapters</h3><p>There are two new chapters in the <cite>JDataStore Developer's Guide</cite>. </p><ul><li>The "What's New" chapter lists the new features and provides links into those topics in the book.</li><li>The "JDataStore Server Console" chapter provides details about the new Server Console interface and the things you can do with it.</li></ul><h3><a name="exapnd_sql"></a>Expanded SQL Reference</h3><p>The JDataStore implementation of the SQL language has been greatly enriched, and the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite> has been expanded and reorganized.</p><h3><a name="escape"></a>JDBC escape syntax</h3><!--BNDX="JDBC escape sequences;JDataStore tables:string functions;JDataStore tables:JDBC escape sequences;literals in JDBC escape sequences"--><p>The JDBC escape syntax was not previously documented. It is now in the "JDBC escape syntax" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jdbc_resultset"></a>Stored procedures and JDBC ResultSets</h3><!--BNDX="JDBC result set;result set, JDBC;returning a JDBC result set"--><!--BNDX="JDBC DataSets;DataSets, returning"--><p>A Java stored procedure can produce a <code>ResultSet</code> on the client by returning either a <code>ResultSet</code> or a DataExpress <code>DataSet</code> from the Java implementation of the stored procedure. The <code>DataSet</code> is automatically converted to a <code>ResultSet</code> for the user of the stored procedure.</p><p>Documentation on the feature has been expanded in JDataStore 7. For more information, see "Stored procedures and JDBC ResultSets" in the "Stored Procedures and UDFs" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="start"></a>Getting started with JDataStore 7</h2><h3><a name="migration"></a>Migrating older databases to JDataStore 7</h3><p>The big issue in migrating older databases to JDataStore 7 is that JdataStore 7 has the concept of schemas, and older databases do not. In JDataStore 7, every table belongs to a schema: the schema name is part of the table name. In general, when a user creates an object such as a table or a view, that object belongs to the user's own schema. There are a number of issues regarding the use of schemas. It will be helpful to you to read <code>CREATE SCHEMA</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> to understand how JDataStore 7 uses schemas before proceeding with migration.</p><p>For additional detail on migrating older JDataStore databases to JDataStore 7, see "Migrating older databases to JDataStore 7" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jb_bes"></a><strong>Using JDataStore 7 with JBuilder and the Borland Enterprise Server</strong></h3><p>To make the latest version of JDataStore available to JBuilder and the Borland Enterprise Server (BES), you need to copy certain files form the JDataStore <em>lib</em> directory to the <em>lib</em> directory of the target product. The files are: <em>beandt.jar</em>, <em>dbtools.jar</em>, <em>dx.jar</em>, <em>jds.jar</em>, <em>jdsremote.jar</em>, and <em>jdsserver.jar</em></p><p>For more information, see "Using JDataStore with JBuilder and the Borland Enterprise server" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><p>Field test note: For the field test, copying these files may cause some menu problems in JBuilder. These problems go away when you remove the copied files. This defect will be fixed for the final release.</p><h2>Change listing for each point release.</h2><h3><a name="fixed_706">Bugs Fixed in 7.06</a></h3><ul><li>Mac installer has been replaced with an installer for intel Mac platform. PowerPC mac's are no longer supported.</li></ul><ul><li>Certain prepared queries with aggregators resulted in bad data.</li></ul><ul><li>Certain prepared queries with an IN operator resulted in a sporadic NullPointer exception. Safeguards have been added.</li><li>If a range is specified in the WHERE clause for an autoincrement column, the wrong rows might be returned. This is also true for certain primary key columns that implicitly are converted into auto increment columns.</li><li>JDataStore 7.006 has been certified for Microsoft Vista. We recommend that the developer edition of JDataStore be installed outside of the “Program Files” directory. The JDataStore .exe launchers depend on config files that are located in the same directory as the launcher.exe. If the product is installed in the “Program Files” directory and Vista UAC is enabled, the changes to the config files will only take affect for the user that makes the modifications. Note that this is mostly of concern to developers or server side installations that use one of the exe launchers. These are the exe Launchers installed by the developer edition of JDataStore: JdsServer*.exe, isql.exe, JdsExplorer*.exe, and ServerConsole*.exe. Note that there are no issues for installing JDataStore jar files in the “Program Files” directory.</li><li>Data corruption from sql update statements under high concurrency environments has been fixed.<li></li>Thread deadlock in JdbcConnectionPool shutdown method that occurs when another thread is also returning a connection to the pool by calling java.sql.Connection.close method has been fixed.</li><li>ArrayIndexOutOfBoundsException that occurs for descending sort operations on String columns</li><li>Prepared statement with grouping criteria may produce incorrect results the second time it is executed when other statements that use the same table are prepared and executed.</li><li>Joins with range selection criteria for more than one table on columns with the same ordinal position can encounter value access errors indicating a type mismatch.</li><li>DB_ADMIN.GET_CONNECTIONS() built in stored procedure will now include local connections in addition to remote connections. This includes connections open with the DataStoreConnection and DataStore components. Connections with a "USER" column that starts with "sys." and connections that have a "REMARKS" column value of "Opener" are internal connections that do not keep a database from shutting down.</li> <h3><a name="fixed_705">Bugs Fixed in 7.05</a></h3><ul><li>An UPDATE query which uses an aggregation of a subquery with an outer reference to set a column value could cause a NullPointerException.</li><li>DatabaseMetaData.getIndexInfo() returned wrong information about auto increment columns.</li><li>A combination of a 1-1 query of 2 tables with single integer column primary keys and an IN operator in the WHERE clause could cause an Exception.</li><li>Creating a table with a single integer column primary key and a different column as an auto increment column, will cause the auto increment column to not function.</li><li>Applications that close connections without closing open statements will incur a memory leak if the statements had executed queries that return ResultSets.</li><li>SQL queries with an “in clause” selection criteria that references an indexed column may not return all rows that satisfy the in clause selection criteria.</li><li>Table open and close operations can fail if several connections are rapidly opening and closing connections.  This can also cause connection close operations to fail resulting in "lingering" connections in the DataStoreServer.</li><li>Statement caching provided by the connection pool does not properly cache or close statements. Because resources and ResultSets are not closed until these unclosed statements are finalized, this can lead to out of memory conditions and large temporary database file sizes.</li><li>For encrypted databases, the crash recovery system can encrypt modified blocks of the user table. This is a mistake because the user table is the one table that cannot be encrypted in an encrypted database. Note that this will only occur if some change is made to the user table since the last time the database was opened. This problem can prevent the database from being opened or cause the user table to appear corrupt when database verification is performed. We are working on a repair method for applications that have encountered this problem.</li><li>Support for opening encrypted databases that have part or all of the user table encrypted by the defect described above. If the user table record for the user connecting is encrypted, the database cannot be opened. In this case there is a new connection property called "priorFileName" that can be used to provide the name of a prior version of the encrypted database that can still be opened. This can be specified as an extended JDBC property for JDBC connections. There is also a DataStoreConnection.setPriorFileName as well. Note that the prior database will only be used to unencrypt the user table that is not supposed to be encrypted in the first place. If the user logging in does not have startup rights in both the prior and current database, the prior database will not be used for the open operation. Once the database affected by this defect has been opened, it should be copied or packed into a new database file.</li></ul> <h3><a name="fixed_704">Bugs Fixed in 7.04</a></h3><ul><li>When "Tools | Encrypt JDataStore" or "Tools | Copy JDataStore" is selected from JdsExplorer, the resulting database has multiple entries for the SYSDBA user. This problem has been fixed.</li><li>When combining an "order by" and an "in" and a sub select on a large set of records, it may result in an incorrect record count.</li></ul> <h3><a name="fixed_703">Bugs Fixed in 7.03</a></h3><h4>Support for Hibernate</h4><ul><li>Hibernate's automated test suites completed. Hibernate dialect class provided in samples directory.</li></ul><h4>General defect corrections and improvements</h4><ul><li>ADMINISTRATOR is now a non reserved keyword in SQL. (It used to be a reserved keyword.)</li><li>Corrected defect in remote driver where retrieving longer string or blob values sometimes caused the driver to hang. </li><li>Database check point events are now logged in the *STATUS * log files. These messages provide "remarks" on what is keeping a log file from being dropped. This can be useful when trying to diagnose why log files are not being automatically dropped. </li><li>New ExtendedProperties.REMARKS property. This can be set to an informative string. This is displayed in many of the contexts in which user name is displayed. Many applications use the same user for many connections. The remarks property makes it easier to distinguish connections that use the same user name. Remarks is displayed for lock error reporting, DB_ADMIN.GET_CONNECTIONS() builtin stored procedure and the connections node of the ServerConsole. </li></ul><h4>SMP support</h4><ul><li>Completion of all automated stress tests on dual processor Windows XP and Redhat Enterprise Linux 3. </li></ul><h4>High availability corrected defects and improvements</h4><ul><li>General stability improvements. </li><li>Improved performance for mirror synchronization. </li><li>Eliminated problems where log files would never drop for databases with mirrors in certain situations. </li><li>Mirrors with the INSTANT_SYNCH or AUTO_FAIL_OVER property set will automatically have a mirror schedule item added to the SYS.MIRROR_SCHEDULE table. This mirror schedule item is added when the mirror is created or when the INSTANT_SYNCH or AUTO_FAIL_OVER property is altered for a mirror that does not already have a mirror schedule item. This default mirror schedule item will synchronize the mirror every 10 seconds. This mirror schedule item can be dropped or altered after the mirror is created if so desired. However, it is probably best to keep a mirror schedule item for each mirror so that the read only mirror database is kept up to date with the primary mirror. When INSTANT_SYNCH or the AUTO_FAIL_OVER property is set for a read only mirror its log records are constantly kept in synch with the primary mirror. However, these log records are not replayed against the read only mirror database until a synch operation is performed. The mirror schedule item will synch the mirror on a regular basis keeping the state of the read only mirror database very close or equal to the state of the primary mirror. Two key benefits of having the readonly mirror databases up to date with the primary mirror are: 1) Fail over (manual or automatic) is much faster because little or no log records need to be replayed before the fail over operation. 2) Readonly mirror databases will reflect a more recent state of the database. This will be important for applications that off load readonly queries from the primary mirror to readonly mirrors. </li><li>ISQL show ddl command now outputs the sql call statements to recreate any mirrors configured for the database. This is useful to see how mirrors are can be created from executing a sql script. </li><li>The last known replay column for the mirrors table and mirror status table in the ServerConsole now displays these values in hex. The high 32 bits are the log file and the low 32 bits are the offset into the log files. These values determine when log files can be automatically dropped. For example a primary mirror cannot drop a log if a read only mirror has not replayed the contents of that log file. So if the last known replay for a read only mirror as a low log file for its last replay column, this will keep this log file and all log files greater than this log file from being dropped. </li></ul> <h3><a name="fixed_702">Bugs Fixed in 7.02</a></h3><ul><li>There have been many significant improvements in High availability Mirrors as well as Read-Only Transactions. </li><li>Mirroring support now drops unneeded log files when it should. </li><li>Cannot use export or show ddl command when a database has multiple schemas because there are no schema creation statements emitted. Insert statements for export also need to prefix table names with schema name. This problem has been fixed. </li><li>DatabaseMetadata now show a foreign keys for other schemas when logging in as SYSDBA. </li><li>ADMIN is still a keyword, but not a reserved one. </li><li>When two separate threads are allocating a new log file at the same time, the potential for a deadlock no longer occurs. </li><li>SHOW DDL did not generate "CREATE SCHEMA" statements. This is needed if the output is to be executed against another database. </li> <li>Foreign keys are now reported in show ddl for non-default schema when logged in as sysdba (administrator). </li><li>Show ddl command now works for a table with an autoincrement column. </li><li>An exception is reported when there are two tables with foreign keys that reference each other, and both tables are being updated by separate transactions a lock timeout error can occur. This has been fixed. </li><li>Wrong result from running join query has been fixed. </li></ul> <h3><a name="fixed_701">Bugs Fixed in 7.01</a></h3><ul><li>Modify output of date and time to include at least 2 digits for day, month, minute, second, hours. </li><li>Remote JDBC driver improved server exception handling. </li><li>A prepared query with a parameterized LIKE operator in the where clause e.g. "SELECT * FROM PERSON WHERE LASTNAME LIKE ?"was mistakenly executed with the parameter given first time the query was executed; thus subsequent executions would receive wrong results. This problem has been fixed. </li><li>A SQL query which uses an auto-increment field for a lookup or join may in certain circumstances yield the wrong result. This problem has been fixed. </li><li>Tables with a column named INTERNALROW, could not be exported using ISQL. This problem has been fixed. </li><li>The data presented in the ServerConsole and the SQL tab in JdsExplorer for a query like: "SELECT * FROM MY_VIEW" could not be edited even if the view was updateable. This problem has been fixed. </li><li>TxException LOCK_TIMEOUT errors fixed for situations where table lock escalation is triggered to max row locks exceeded. </li><li>Problem when value from source cursor had a maxInline setting that was larger than the destination cursor. Cursor now can convert inline into blob if necessary. </li><li>Drop column no longer fails to have any affect if another connection has a prepared statement that references the same table. </li><li>The command SHOW TABLE in ISQL required an explicit schema name. This problem has been fixed. </li><li>Cannot drop primary mirror. Problem is now fixed. </li> <li>ResultSetMetaData now returns the correct column count when an updateable ResultSet is used. </li><li>Column from Primary keys were sometimes reported to be nullable through DatabaseMetadata.getColumns().This problem has been fixed. </li><li>If 2 timestamp values are given as 2 literals the first value is stored for both values. This problem has been fixed. </li><li>The Date and Timestamp literal JDBC escape formats were incorrectly documented. This problem has been fixed. </li></ul> http://cc.embarcadero.com/Item/25369 2008-05-13T22:18:36 2008-05-13T22:18:36 http://cc.embarcadero.com/Item/25369 <h1 align="center"><a name="_top_"></a>JDataStore 7.06 (build 7.006.039) for Solaris<br>Release Notes</h1><p>These Release Notes provide a brief description of each new feature in JDataStore 7.The <cite>JDataStore Developer's Guide</cite> includes a "What's New" chapter that provideslinks to the documentation for each new feature within the Developer's Guide.</p><p><strong>Bug fix list</strong></p><ul><li>To see bugs fixed in JDataStore 7.06 click <a href="#fixed_706">here</a></li><li>To see bugs fixed in JDataStore 7.05 click <a href="#fixed_705">here</a></li><li>To see bugs fixed in JDataStore 7.04 click <a href="#fixed_704">here</a></li><li>To see bugs fixed in JDataStore 7.03 click <a href="#fixed_703">here</a></li><li>To see bugs fixed in JDataStore 7.02 click <a href="#fixed_702">here</a></li><li>To see bugs fixed in JDataStore 7.01 click <a href="#fixed_701">here</a></li></ul><p><strong>New Features</strong></p><ul><li><a href="#failsafe">The JDataStore High Availability Server: incremental backup, automatic failover</a></li><li>The new <a href="#console">Server Console</a> graphical interface</li></ul><p><strong>New SQL functions</strong></p><ul><li><a href="#bit_length"><code>BIT_LENGTH</code></a></li><li><a href="#case_function"><code>CASE</code></a></li><li><a href="#coalesce"><code>COALESCE</code></a></li><li><a href="#current_role"><code>CURRENT_ROLE</code></a></li><li><a href="#current_user"><code>CURRENT_USER</code></a></li><li><a href="#db_admin"><code>DB_ADMIN</code></a></li><li><a href="#DB_UTIL"><code>DB_UTIL</code></a></li><li><a href="#nullif"><code>NULLIF</code></a></li><li><a href="#octet_length"><code>OCTET_LENGTH</code></a></li><li><a href="#user_function"><code>USER</code></a></ul><p><strong>New and updated SQL statements</strong></p><ul><li><a href="#create_schema"><code>CREATE SCHEMA</code></a>, <a href="#drop_schema"><code>DROP SCHEMA</code></a></li><li><a href="#create_view"><code>CREATE VIEW</code></a>, <a href="#alter_view"><code>ALTER VIEW</code></a>, <a href="#drop_view"><code>DROP VIEW</code></a></li><li><a href="#create_role"><code>CREATE ROLE</code></a>, <a href="#set_role"><code>SET ROLE</code></a>, <a href="#drop_role"><code>DROP ROLE</code></a></li><li>New <code><a href="#create_table">CREATE TABLE</a></code> options</li><li>New <code><a href="#alter_table">ALTER TABLE</a></code> options</li><li>New <code><a href="#drop_table">DROP TABLE</a></code> options: <code>CASCADE</code> and <code>RESTRICT</code></li><li><a href="#create_java_class"><code>CREATE JAVA_CLASS</code></a>, <code><a href="#drop_java_class">DROP JAVA_CLASS</a></code></li></ul><p><strong>Security management</strong></p><ul><li><code><a href="#grant_statement">GRANT</a></code> and <code><a href="#revoke_statement">REVOKE</a></code></li><li><code><a href="#create_user">CREATE USER</a></code>, <code><a href="#alter_user">ALTER USER</a></code>, <code><a href="#drop_user">DROP USER</a></code></li></ul><p><strong>Transaction management</strong></p><ul><li><code><a href="#set_transaction">SET TRANSACTION</a></code></ul><p><strong>Other new SQL</strong></p><ul><li><a href="#keywords">New keywords</a></li><li>New data type: <a href="#tinyint"><code>TINYINT</code></a></li><li>Many new <a href="#escape_functions">JDBC escape functions</a></li><li><a href="#isql">ISQL cross-platform SQL command-line utility</a></li></ul><p><strong>Product notes</strong></p><ul><li><a href="#choose">Choosing between Server Console and JdsExplorer</a></li><li><a href="#change_copy">A change to the "Copy JDataStore" menu item</a></li></ul><p><strong>New and updated documentation</strong></p><ul><li><a href="#new_chaps">New chapters</a></li><li><a href="#escape">Escape syntax for calling stored procedures</a> is now documented.</li><li>Updated documentation on <a href="#jdbc_resultset">returning JDBC ResultSets</a></li></ul><p><strong>Getting started with JDataStore 7</strong></p><ul><li><a href="#migration">Migrating older databases to JDataStore 7</a></li><li><a href="#jb_bes">Using JDataStore 7 with JBuilder and the Borland Enterprise server</a></li></ul><!-- <p><a href="#bugs">Defects fixed in JDataStore 7</a></p> --><!-- <h2><a name="features"></a>New features</h2> --><h2><a name="features"></a>New features</h2><h3><a name="failsafe"></a>The JDataStore High Availability Server</h3><p>JDataStore 7 provides tools for creating automatic or manual incremental backups and for creating automatic failover to a mirror of the original database in case of failure. In addition, there are tools for viewing and managing connections on a remote server, for managing datasources and connections graphically or with the new ISQL feature, for viewing database status logs and transactions logs, for viewing logs, and for verifying databases.</p><p>The "High Availability Server" topic in the "Architecture" chapter of the <cite>JDataStore Developer's Guide</cite> discusses the architecture of JDataStore's new failsafe server and its associated mirroring functionality. This section is well worth reading, because it will help you make the most of this new offerings. </p><p>For a description of how to use JDataStore's new Server Console to access this new functionality, see the new "JDataStore Server Console" chapter in the <cite>JDataStore Developer's Guide</cite>. </p> <h3><a name="console"></a>The new Server Console graphical interface</h3><p>There is a whole new graphical interface in JDataStore 7. The Server Console performs many server administration tasks, including several that are new in JDataStore 7, such as automatic failover and incremental backup.</p><p>Here is an overview of what you can do with the Server Console. The items in the following list are topics in the "JDataStore Server Console" chapter of the <cite>JDataStore Developer's Guide</cite> for details.</p><ul><li><strong>Overview</strong> Get a quick overview of what you can do with Server Console</li><li><strong>About datasources</strong> If you're not familiar with how JDataStore uses dataasources to connect to databases, this is the place to find out.</li><li><strong>What you see and what you get</strong> Get familiar with the new Server Console interface.</li><li><strong>Starting/shutting down the server</strong> You can use Server Console to start and stop the local server.</li><li><strong>Connection settings</strong> A detailed description of how to create, modify, and delete datasources, and how to connect to and disconnect from them.</li><li><strong>Creating and managing datasources</strong> Create, rename, and modify datasources, connect to them, and disconnect from them.</li><li><strong>Verifying a database</strong> Server Console makes it easier than ever.</li><li><strong>Managing connections</strong> View and optionaly terminate both local and remote datasources.</li><li><strong>Managing database properties</strong> See an editable grid of database properties for both local and remote connections.</li><li><strong>Viewing table and row locks</strong> Server Console makes it easy to see what's happening with locks on both the local and remote server.</li><li><strong>Viewing the database status log file</strong> You exactly what's been going on with a server by viewing its server status file.</li><li><strong>Failover</strong> and <strong>incremental backup</strong> Use mirrors to protect against failures and to incrementally backup your data on a schedule of your choosing. Using Server Console, you can add </li><li><strong>Interactive SQL</strong> A special SQL pane lets you run SQL or SQL scripts against connected datasources.</li></ul><p><strong>What happened to the old JdsServer graphical interface?</strong> It's still there, but it has been replaced by the new Server Console. You can still start the JDataStore server as an application by running the <code>JdsServer</code> executable. However, it is now set to run without the GUI. If you really need that deprecated interface back, you can invoke the GUI by executing the following command:</p><table class="pre"><tr><td><pre>jdsserver -ui [windows|motif|metal|none][other parameters]</pre></td></tr></table><p>Choose the interface that is appropriate for your platform. For more about starting the JDataStore server, see "Launching JdsServer" in the "JDataStore Administration" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="keywords"></a>New keywords</h3><p>The asterisk following a keyword indicates that the keyword is <em>reserved</em>. Reserved keywords can be used as SQL identifiers only if they are enclosed in double quotation marks. When quoted in this fashion, they are case sensitive. The words that have no asterisk are <em>nonreserved</em> keywords. They can be used with or without double quotes and are case insensitive when note in quotes.</p><p>For a complete list of keywords, see <strong>Keywords</strong> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><table border="0"><tr><td>ADMIN*<br>ADMINISTRATOR*<br>AUTHORIZATION*<br>BIT_LENGTH*<br>COALESCE*<br>CURRENT_ROLE*<br>CURRENT_USER*<br>EXECUTE*<br>GRANT*<br>ISOLATION*<br></td><td>LEVEL*<br>NONE*<br>NULLIF*<br>OCTET_LENGTH*<br>ONLY*<br>OPTION*<br>PRIVILEGES*<br>PUBLIC*<br>READ<br>RENAME*<br></td><td>RESOLVABLE*<br>REVOKE*<br>ROLE<br>SCHEMA*<br>STARTUP*<br>TO*<br>TRANSACTION*<br>VIEW*<br>WITH*<br>WRITE<br></td></tr></table> <h2><a name="new_funcs"></a>New SQL functions</h2><h3><a name="bit_length"></a>BIT_LENGTH</h3><p>The <code>BIT_LENGTH</code> function gives the length in bits of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>BIT_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="case_function"></a>CASE</h3><!--BNDX="CASE function;SQL functions:CASE"--><p>The <code>CASE</code> function returns a conditional value. For more information, see <code>CASE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="coalesce"></a>COALESCE</h3><!--BNDX="COALESCE function;SQL functions:COALESCE;non-NULL values, returning"--><p>The <code>COALESCE</code> function returns the first non-NULL value from the expression list. For more information, see <code>COALESCE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="current_role">CURRENT_ROLE</a></h3><!--BNDX="CURRENT_ROLE function;SQL functions:CURRENT_ROLE;roles"--><p>The <code>CURRENT_ROLE</code> function returns the current role, or NULL if no role has been set using the <code>SET ROLE</code> statement. For more information, see <code>CURRENT_ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. </p><h3><a name="current_user"></a>CURRENT_USER</h3><!--BNDX="CURRENT_USER function;SQL functions:CURRENT_USER"--><p>The <code>CURRENT_USER</code> function returns the name of the current user. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="db_admin"></a>DB_ADMIN: administration functions</h3><!--BNDX="DB_ADMIN function;SQL functions:DB_ADMIN"--><p><code>DB_ADMIN</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. Use <code>DB_ADMIN</code> for various database administration tasks such as automatic failover, incremental backup, creating and managing datasources, viewing and managing connections, verifying tables, and displaying database privileges and properties, locks, status logs, procedure privileges, and roles granted.</p><p><code>DB_ADMIN</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method, implemented as a SQL function. The description of each method includes a link to the exact implementation and <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_ADMIN</code> provides the following methods:</p><table border="0" cols="3"><tr><td><code>ALTER_DATABASE<br>ALTER_MIRROR<br>ALTER_MIRROR_SCHEDULE<br>CLOSE_CONNECTION<br>CREATE_MIRROR<br>CREATE_MIRROR_SCHEDULE<br>DROP_MIRROR<br>DROP_MIRROR_SCHEDULE<br>GET_CONNECTIONS<br>GET_DATABASE_PRIVILEGES<br>GET_DATABASE_PROPS<br>GET_DATABASE_STATUS_LOG_FILTER<br>GET_LOCKS</code></td><td><code>GET_MIRRORS<br>GET_NEWEST_STATUS_LOG_ID<br>GET_OLDEST_STATUS_LOG_ID<br>GET_PROCEDURE_PRIVILEGES<br>GET_ROLE_GRANTS<br>GET_STATUS_LOG_FILTER<br>GET_STATUS_LOG<br>GET_THIS_MIRROR<br>SET_DATABASE_STATUS_LOG_FILTER<br>SET_PRIMARY_MIRROR<br>SET_STATUS_LOG_FILTER<br>SYNCH_MIRROR<br>VERIFY</code> </td></tr></table> <br> <h3><a name="DB_UTIL"></a>DB_UTIL: numeric, string, and date/time functions</h3><!--BNDX="DB_UTIL functions;SQL functions:DB_UTIL;math functions;string functions;date/time functions;utilities:DB_UTIL"--><p><code>DB_UTIL</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. They are a collection of SQL utility functions that perform numeric, string and date/time operations on data stored in database tables. </p><p><code>DB_UTIL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method. The description of each method includes a link to the exact implementation in <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_UTIL</code> provides the following methods</p><table border="0"><tr><td><code><br>ACOS<br>ASIN<br>ATAN<br>ATAN2<br>CEILING<br>COS<br>COT<br>DEGREES<br>EXP<br>FLOOR<br>LOG<br>LOG10<br>MOD<br>PI</code></td><td><br><code>POWER<br>RADIANS<br>RAND<br>ROUND<br>SIGN<br>SIN<br>SQRT<br>TAN<br>TRUNCATE<br>ASCII<br>TO_CHAR<br>DIFFERENCE<br>INSERT_STRING<br>LEFT_STRING</code></td><td><code><br>REPEAT<br>REPLACE<br>RIGHT<br>SOUNDEX<br>SPACE<br>DAYNAME<br>DAYOFWEEK<br>DAYOFYEAR<br>MONTHNAME<br>QUARTER<br>TIMESTAMPADD<br>TIMESTAMPDIFF<br>WEEK</code></td></tr></table> <br> <h3><a name="nullif"></a>NULLIF</h3><!--BNDX="NULLIF function;SQL functions:NULLIF;expressions:comparing;comparisons:expressions with NULLIF"--><p>The <code>NULLIF</code> function compares two expressions. It returns NULL if the expressions are equal. Otherwise, it returns the first expression. It is logically equivalent to the following <code>CASE</code> expression: <code>CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END</code><br><br>For more information, see <code>NULLIF</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="octet_length"></a>OCTET_LENGTH</h3><!--BNDX="OCTET_LENGTH function;SQL functions:OCTET_LENGTH;length of string, imput stream, or object"--><p>The <code>OCTET_LENGTH</code> function gives the length in bytes of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>OCTET_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="user_function"></a>USER</h3><!--BNDX="USER function;SQL functions:USER"--><p>The <code>USER</code> function returns the name of the current user; this function is the same as <code><a href="#current_user">CURRENT_USER</a></code>. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="new_sql"></a>New and updated SQL statements</h2><h3><a name="create_schema"></a>CREATE SCHEMA</h3><!--BNDX="CREATE SCHEMA statement;schemas:creating;SQL statements:CREATE SCHEMA"--><!--BNDX="statements, <em>see</em> SQL statements"--><p>The <code>CREATE SCHEMA</code> statement creates a name space for tables, views, and methods. You can use <code>CREATE SCHEMA</code> to create multiple objects in one SQL statement. For a discussion of how schemas work in JDataStore, see <code>CREATE SCHEMA</code> and <code>DROP SCHEMA</code>in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_schema"></a>DROP SCHEMA</h3><!--BNDX="DROP SCHEMA statement;schemas:dropping;SQL statements:DROP SCHEMA"--><p>The <code>DROP SCHEMA</code> statement deletes the specified schema. If the command is used without options, it is the same as specifying the <code>RESTRICT</code> option: the schema to be dropped must be empty. The command fails if the schema contains any objects. </p> <p class="bscan"><span class="bscan">Note: </span>The <code>DROP SCHEMA</code> command used with the <code>CASCADE</code> option is extremely powerful and should be used with caution. When this command is issued, it drops the schema and all of its objects and dependencies without any chance to change your mind. There is no undo.</p> <h3><a name="create_view"></a>CREATE VIEW</h3><!--BNDX="CREATE VIEW statement;SQL statements:CREATE VIEW;views:creating"--><p>The <code>CREATE VIEW</code> statement creates a derived table by selecting specified columns from existing tables. Views provide a way of accessing a consistent subcollection of the data stored in one or more tables. When the data in the underlying tables changes, the view reflects this change.</p>For more information, see <code>CREATE VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="alter_view"></a>ALTER VIEW</h3><!--BNDX="ALTER VIEW statement;SQL statements:ALTER VIEW;views:altering"--><p>The <code>ALTER VIEW</code> statement modifies a view without losing dependent views and existing <code>GRANT</code>s. This statement can be used to change the name of a view, the columns that comprise the view, and whether the view has the <code>WITH CHECK OPTION</code> constraint. For more information, see <code>ALTER VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_view"></a>DROP VIEW</h3><!--BNDX="DROP VIEW statement;SQL statements:DROP VIEW;views:dropping"--><p>The <code>DROP VIEW</code> statement drops the named view. By default, it fails if there are dependencies on the view. The <code>CASCADE</code> option drops the view and any dependent views. For more information, see <code>DROP VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_role"></a>CREATE ROLE</h3><!--BNDX="CREATE ROLE statement;SQL statements:CREATE ROLE;roles:creating;privileges:roles"--><p>The <code>CREATE ROLE</code> statement creates a named role. To complete this functionality, you must <code>GRANT</code> privileges to the role, and <code>GRANT</code> the role to one or more users. To make use of the privileges acquired in this fashion, the user issues a <code>SET ROLE</code> statement.</p><p>For more information, see <code>CREATE ROLE</code> and the <code>GRANT</code> statement in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="set_role"></a>SET ROLE</h3><!--BNDX="SET ROLE statement;SQL statements:SET ROLE;roles:activating;privileges:roles"--><p>The <code>SET ROLE</code> statement makes the named role active. The current user acquires all privileges assigned to that role. For more information, see <code>SET ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_role"></a>DROP ROLE</h3><!--BNDX="DROP ROLE statement;SQL statements:DROP ROLE;roles:dropping"--><p>The <code>DROP ROLE</code> statement drops the specified role. For more information, see <code>DROP ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_table"></a>CREATE TABLE</h3><!--BNDX="CREATE TABLE statement;JDataStore tables:creating;foreign keys;SQL statements:CREATE TABLE"--><!--BNDX="schemas:creating tables in;JDataStore tables:schemas"--><p>There are three new options for the <code>CREATE TABLE</code> statement:</p><ul><li>The table name now incldues a schema name.</li><li>You have the option of specifying a position for each column.</li><li>You can use the [NOT] RESOLVABLE option to track data changes for DataExpress.</li></ul><p>For more information, see <code>CREATE TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_table"></a>ALTER TABLE</h3><!--BNDX="ALTER TABLE statement;JDataStore tables:modifying;SQL statements:ALTER TABLE"--><p>There are several new options for the <code>ALTER TABLE</code> statement:</p><ul><li>You can rename the entire table; this is how you assign a table to a different schema.</li><li>You can make the table <code>RESOLVABLE</code> or <code>NOT RESOLVABLE</code>.</li><li>At the column level you can:<ul><li>Change the datatype of a column</li><li>Set whether a collumn is nullable</li><li>Rename a column</li><li>Change the position of a column within the table</li></ul></li></ul><p>For more information, see <code>ALTER TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_table"></a>DROP TABLE</h3><!--BNDX="DROP TABLE statement;SQL statements:DROP TABLE;JDataStore tables:deleting"--><p>The <code>DROP TABLE</code> statement deletes a table and its indexes from a JDataStore database. <code>DROP TABLE</code> has two new options: <code>RESTRICT</code> and <code>CASCADE</code>.</p> <h3><a name="create_java_class"></a>CREATE JAVA_CLASS</h3><!--BNDX="CREATE JAVA_CLASS statement;SQL statements:CREATE JAVA_CLASS;Java classes:creating;creating:java classes"--> <p>The <code>CREATE JAVA_CLASS</code> statement makes all public static methods of a Java class available to JDataStore SQL as stored procedures or UDFs. For more information, see <code>CREATE JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="drop_java_class"></a>DROP JAVA_CLASS</h3><!--BNDX="DROP JAVA_CLASS statement;SQL statements:DROP JAVA_CLASS;Java classes:dropping;dropping:java classes"--> <p>The <code>DROP JAVA_CLASS</code> statement drops a stored class, making it unavailable for use in JDataStore SQL. For more information, see <code>DROP JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="grant_statement"></a>GRANT</h3><!--BNDX="GRANT statement;SQL statements:GRANT;database privileges, granting;privileges:granting;roles:granting privileges to;roles:granting to users"--><p>The <code>GRANT</code> statement performs the following actions:</p><ul><li>It grants object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods to <code>PUBLIC</code>, users, or roles.</li><li>It grants database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—to users or roles.</li><li>It grants roles to users or roles.</li></ul>For more information, see <code>GRANT</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="revoke_statement"></a>REVOKE</h3><!--BNDX="REVOKE statement;SQL statements:REVOKE;database privileges, revoking;roles:revoking privileges"--><p>The <code>REVOKE</code> statement performs a number of actions:</p><ul><li>It revokes object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods from <code>PUBLIC</code>, users, or roles. It has <code>CASCADE</code> and <code>RESTRICT</code>,options.</li><li>It revokes database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—from users or roles.</li><li>It revokes roles from users or roles.</li><li>It revokes the <code>ADMIN</code> option from a role without revoking the role itself.</li><li>It revokes the <code>GRANT</code> option from a privilege without revoking the privilege itself.</li></ul><p>For more information, see <code>REVOKE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_user"></a>CREATE USER</h3><!--BNDX="CREATE USER statement;SQL statements:CREATE USER;users:adding with CREATE USER"--><p>The <code>CREATE USER</code> statement adds the named user and associated password to the database. The password is case sensitive, the user name is not. For more information, see <code>CREATE USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_user"></a>ALTER USER</h3><!--BNDX="ALTER USER statement;SQL statements:ALTER USER;users:editing with ALTER USER"--><p>The <code>ALTER USER</code> statement sets a new password for an existing user. For more information, see <code>ALTER USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_user"></a>DROP USER</h3><!--BNDX="DROP USER statement;SQL statements:DROP USER;users:removing with DROP USER"--><p>The <code>DROP USER</code> statement drops a user and all objects that the user owns. It has <code>RESTRICT</code> and <code>CASCADE</code> options. For more information, see <code>DROP USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="set_transaction"></a>SET TRANSACTION</h3><!--BNDX="SET TRANSACTION statement;SQL statements:SET TRANSACTION;transactions: setting; transaction isolation levels, overview;isolation levels:setting"--><p>The <code>SET TRANSACTION</code> statement sets the properties for the following transaction. You can use it to specify the isolation level and whether the transaction is read-write or read-only. For more information, see <code>SET TRANSACTION</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. See <a href="architecture.html#tx_management">"Transaction management"</a> in the "System Architecture" chapter for further discussion of JDataStore transaction management.</p><h3><a name="tinyint"></a>New data type: TINYINT</h3><p>JDataStore SQL now provides a one-byte integer data type, <code>TINYINT</code> (or <code>BYTE</code>). For more information, see "Datatypes" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="escape_functions"></a>JDBC escape functions</h3><!--BNDX="JDBC escape functions;SQL functions:JDBC escape functions;functions:JDBC escape functions"--><p>JDataStore now provides a greatly expanded list of JDBC escape functions. For a complete list, see "JDBC escape functions" the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="isql"></a>ISQL</h3><p>JDataStore's new ISQL can be run in the SQL tab of the Server Console. These commands can also be issued from any system command console.</p><p>For a discussion of JDataStore new ISQL and a list of commands, see <code>ISQL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="notes"></a>Product notes</h2><h3><a name="choose"></a>Choosing between JdsExplorer and the Server Console</h3><p>The Server Console is a graphical interface that is new in JDataStore 7. In it, you can perform some of the tasks that you previously performed in JdsExplorer. In addition, Server Console provides access to many new features.</p><p>From Server Console you can:</p><ul><li>Create and edit datasources, connect to local or remote databases, and view and manage connections. </li><li>View and manage database properties, and view database status logs, view table and row locks. and verify databases. You cannot create databases in Server Console.</li><li>Create and manage mirrors for incremental backup, auto failover, and load balancing.</li><li>Use the ISQL tab to execute all SQL and ISQL commands. There is a list of ISQL commands at the end of the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite>. JdsExplorer off an environment for executing SQL commands, but you cannot execute ISQL commands there.</li></ul><p>You need JdsExplorer if you want to:</p><ul><li>Perform user administration</li><li>Manage license keys</li><li>Work with and view table structure and content, including indexes.</li><li>Import tables from other databases and import text and images into a database</li><li>Upgrade, downgrade, copy, encrypt/decrypt or pack a database. Database verification can be performed from either JdsExplorer or Server Console.</li></ul><p>Most of the tasks listed for JdsExplorer can be performed in the Server Console using the ISQL window.</p><h3><a name="change_copy"></a>A change to the "Copy JDataStore" menu item</h3><p>JdsExplorer has a Copy JDataStore item on the Tools menu. Its function is different in JDataStore 7 then in earlier versions of the product. In previous versions of JDataStore, choosing Tools|Copy JDataStore brought up the Copy Streams dialog box, and made you select exactly which streams to copy. Now this menu item brings up a dialog in which you copy an entire database file.</p><p>There is a new item on the JDataStore Tools menu: Copy Into Existing JDataStore. This item permits you to copy into an existing, empty JDataStore, which allows you to downgrade or encrypt databases.</p><p>To copy individual tables between databases, use the Tools|Import chose in JdsExplorer.</p> <h2><a name="new_doc"></a>New and updated documentation</h2><h3><a name="new_chaps"></a>New chapters</h3><p>There are two new chapters in the <cite>JDataStore Developer's Guide</cite>. </p><ul><li>The "What's New" chapter lists the new features and provides links into those topics in the book.</li><li>The "JDataStore Server Console" chapter provides details about the new Server Console interface and the things you can do with it.</li></ul><h3><a name="exapnd_sql"></a>Expanded SQL Reference</h3><p>The JDataStore implementation of the SQL language has been greatly enriched, and the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite> has been expanded and reorganized.</p><h3><a name="escape"></a>JDBC escape syntax</h3><!--BNDX="JDBC escape sequences;JDataStore tables:string functions;JDataStore tables:JDBC escape sequences;literals in JDBC escape sequences"--><p>The JDBC escape syntax was not previously documented. It is now in the "JDBC escape syntax" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jdbc_resultset"></a>Stored procedures and JDBC ResultSets</h3><!--BNDX="JDBC result set;result set, JDBC;returning a JDBC result set"--><!--BNDX="JDBC DataSets;DataSets, returning"--><p>A Java stored procedure can produce a <code>ResultSet</code> on the client by returning either a <code>ResultSet</code> or a DataExpress <code>DataSet</code> from the Java implementation of the stored procedure. The <code>DataSet</code> is automatically converted to a <code>ResultSet</code> for the user of the stored procedure.</p><p>Documentation on the feature has been expanded in JDataStore 7. For more information, see "Stored procedures and JDBC ResultSets" in the "Stored Procedures and UDFs" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="start"></a>Getting started with JDataStore 7</h2><h3><a name="migration"></a>Migrating older databases to JDataStore 7</h3><p>The big issue in migrating older databases to JDataStore 7 is that JdataStore 7 has the concept of schemas, and older databases do not. In JDataStore 7, every table belongs to a schema: the schema name is part of the table name. In general, when a user creates an object such as a table or a view, that object belongs to the user's own schema. There are a number of issues regarding the use of schemas. It will be helpful to you to read <code>CREATE SCHEMA</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> to understand how JDataStore 7 uses schemas before proceeding with migration.</p><p>For additional detail on migrating older JDataStore databases to JDataStore 7, see "Migrating older databases to JDataStore 7" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jb_bes"></a><strong>Using JDataStore 7 with JBuilder and the Borland Enterprise Server</strong></h3><p>To make the latest version of JDataStore available to JBuilder and the Borland Enterprise Server (BES), you need to copy certain files form the JDataStore <em>lib</em> directory to the <em>lib</em> directory of the target product. The files are: <em>beandt.jar</em>, <em>dbtools.jar</em>, <em>dx.jar</em>, <em>jds.jar</em>, <em>jdsremote.jar</em>, and <em>jdsserver.jar</em></p><p>For more information, see "Using JDataStore with JBuilder and the Borland Enterprise server" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><p>Field test note: For the field test, copying these files may cause some menu problems in JBuilder. These problems go away when you remove the copied files. This defect will be fixed for the final release.</p><h2>Change listing for each point release.</h2><h3><a name="fixed_706">Bugs Fixed in 7.06</a></h3><ul><li>Mac installer has been replaced with an installer for intel Mac platform. PowerPC mac's are no longer supported.</li></ul><ul><li>Certain prepared queries with aggregators resulted in bad data.</li></ul><ul><li>Certain prepared queries with an IN operator resulted in a sporadic NullPointer exception. Safeguards have been added.</li><li>If a range is specified in the WHERE clause for an autoincrement column, the wrong rows might be returned. This is also true for certain primary key columns that implicitly are converted into auto increment columns.</li><li>JDataStore 7.006 has been certified for Microsoft Vista. We recommend that the developer edition of JDataStore be installed outside of the “Program Files” directory. The JDataStore .exe launchers depend on config files that are located in the same directory as the launcher.exe. If the product is installed in the “Program Files” directory and Vista UAC is enabled, the changes to the config files will only take affect for the user that makes the modifications. Note that this is mostly of concern to developers or server side installations that use one of the exe launchers. These are the exe Launchers installed by the developer edition of JDataStore: JdsServer*.exe, isql.exe, JdsExplorer*.exe, and ServerConsole*.exe. Note that there are no issues for installing JDataStore jar files in the “Program Files” directory.</li><li>Data corruption from sql update statements under high concurrency environments has been fixed.<li></li>Thread deadlock in JdbcConnectionPool shutdown method that occurs when another thread is also returning a connection to the pool by calling java.sql.Connection.close method has been fixed.</li><li>ArrayIndexOutOfBoundsException that occurs for descending sort operations on String columns</li><li>Prepared statement with grouping criteria may produce incorrect results the second time it is executed when other statements that use the same table are prepared and executed.</li><li>Joins with range selection criteria for more than one table on columns with the same ordinal position can encounter value access errors indicating a type mismatch.</li><li>DB_ADMIN.GET_CONNECTIONS() built in stored procedure will now include local connections in addition to remote connections. This includes connections open with the DataStoreConnection and DataStore components. Connections with a "USER" column that starts with "sys." and connections that have a "REMARKS" column value of "Opener" are internal connections that do not keep a database from shutting down.</li> <h3><a name="fixed_705">Bugs Fixed in 7.05</a></h3><ul><li>An UPDATE query which uses an aggregation of a subquery with an outer reference to set a column value could cause a NullPointerException.</li><li>DatabaseMetaData.getIndexInfo() returned wrong information about auto increment columns.</li><li>A combination of a 1-1 query of 2 tables with single integer column primary keys and an IN operator in the WHERE clause could cause an Exception.</li><li>Creating a table with a single integer column primary key and a different column as an auto increment column, will cause the auto increment column to not function.</li><li>Applications that close connections without closing open statements will incur a memory leak if the statements had executed queries that return ResultSets.</li><li>SQL queries with an “in clause” selection criteria that references an indexed column may not return all rows that satisfy the in clause selection criteria.</li><li>Table open and close operations can fail if several connections are rapidly opening and closing connections.  This can also cause connection close operations to fail resulting in "lingering" connections in the DataStoreServer.</li><li>Statement caching provided by the connection pool does not properly cache or close statements. Because resources and ResultSets are not closed until these unclosed statements are finalized, this can lead to out of memory conditions and large temporary database file sizes.</li><li>For encrypted databases, the crash recovery system can encrypt modified blocks of the user table. This is a mistake because the user table is the one table that cannot be encrypted in an encrypted database. Note that this will only occur if some change is made to the user table since the last time the database was opened. This problem can prevent the database from being opened or cause the user table to appear corrupt when database verification is performed. We are working on a repair method for applications that have encountered this problem.</li><li>Support for opening encrypted databases that have part or all of the user table encrypted by the defect described above. If the user table record for the user connecting is encrypted, the database cannot be opened. In this case there is a new connection property called "priorFileName" that can be used to provide the name of a prior version of the encrypted database that can still be opened. This can be specified as an extended JDBC property for JDBC connections. There is also a DataStoreConnection.setPriorFileName as well. Note that the prior database will only be used to unencrypt the user table that is not supposed to be encrypted in the first place. If the user logging in does not have startup rights in both the prior and current database, the prior database will not be used for the open operation. Once the database affected by this defect has been opened, it should be copied or packed into a new database file.</li></ul> <h3><a name="fixed_704">Bugs Fixed in 7.04</a></h3><ul><li>When "Tools | Encrypt JDataStore" or "Tools | Copy JDataStore" is selected from JdsExplorer, the resulting database has multiple entries for the SYSDBA user. This problem has been fixed.</li><li>When combining an "order by" and an "in" and a sub select on a large set of records, it may result in an incorrect record count.</li></ul> <h3><a name="fixed_703">Bugs Fixed in 7.03</a></h3><h4>Support for Hibernate</h4><ul><li>Hibernate's automated test suites completed. Hibernate dialect class provided in samples directory.</li></ul><h4>General defect corrections and improvements</h4><ul><li>ADMINISTRATOR is now a non reserved keyword in SQL. (It used to be a reserved keyword.)</li><li>Corrected defect in remote driver where retrieving longer string or blob values sometimes caused the driver to hang. </li><li>Database check point events are now logged in the *STATUS * log files. These messages provide "remarks" on what is keeping a log file from being dropped. This can be useful when trying to diagnose why log files are not being automatically dropped. </li><li>New ExtendedProperties.REMARKS property. This can be set to an informative string. This is displayed in many of the contexts in which user name is displayed. Many applications use the same user for many connections. The remarks property makes it easier to distinguish connections that use the same user name. Remarks is displayed for lock error reporting, DB_ADMIN.GET_CONNECTIONS() builtin stored procedure and the connections node of the ServerConsole. </li></ul><h4>SMP support</h4><ul><li>Completion of all automated stress tests on dual processor Windows XP and Redhat Enterprise Linux 3. </li></ul><h4>High availability corrected defects and improvements</h4><ul><li>General stability improvements. </li><li>Improved performance for mirror synchronization. </li><li>Eliminated problems where log files would never drop for databases with mirrors in certain situations. </li><li>Mirrors with the INSTANT_SYNCH or AUTO_FAIL_OVER property set will automatically have a mirror schedule item added to the SYS.MIRROR_SCHEDULE table. This mirror schedule item is added when the mirror is created or when the INSTANT_SYNCH or AUTO_FAIL_OVER property is altered for a mirror that does not already have a mirror schedule item. This default mirror schedule item will synchronize the mirror every 10 seconds. This mirror schedule item can be dropped or altered after the mirror is created if so desired. However, it is probably best to keep a mirror schedule item for each mirror so that the read only mirror database is kept up to date with the primary mirror. When INSTANT_SYNCH or the AUTO_FAIL_OVER property is set for a read only mirror its log records are constantly kept in synch with the primary mirror. However, these log records are not replayed against the read only mirror database until a synch operation is performed. The mirror schedule item will synch the mirror on a regular basis keeping the state of the read only mirror database very close or equal to the state of the primary mirror. Two key benefits of having the readonly mirror databases up to date with the primary mirror are: 1) Fail over (manual or automatic) is much faster because little or no log records need to be replayed before the fail over operation. 2) Readonly mirror databases will reflect a more recent state of the database. This will be important for applications that off load readonly queries from the primary mirror to readonly mirrors. </li><li>ISQL show ddl command now outputs the sql call statements to recreate any mirrors configured for the database. This is useful to see how mirrors are can be created from executing a sql script. </li><li>The last known replay column for the mirrors table and mirror status table in the ServerConsole now displays these values in hex. The high 32 bits are the log file and the low 32 bits are the offset into the log files. These values determine when log files can be automatically dropped. For example a primary mirror cannot drop a log if a read only mirror has not replayed the contents of that log file. So if the last known replay for a read only mirror as a low log file for its last replay column, this will keep this log file and all log files greater than this log file from being dropped. </li></ul> <h3><a name="fixed_702">Bugs Fixed in 7.02</a></h3><ul><li>There have been many significant improvements in High availability Mirrors as well as Read-Only Transactions. </li><li>Mirroring support now drops unneeded log files when it should. </li><li>Cannot use export or show ddl command when a database has multiple schemas because there are no schema creation statements emitted. Insert statements for export also need to prefix table names with schema name. This problem has been fixed. </li><li>DatabaseMetadata now show a foreign keys for other schemas when logging in as SYSDBA. </li><li>ADMIN is still a keyword, but not a reserved one. </li><li>When two separate threads are allocating a new log file at the same time, the potential for a deadlock no longer occurs. </li><li>SHOW DDL did not generate "CREATE SCHEMA" statements. This is needed if the output is to be executed against another database. </li> <li>Foreign keys are now reported in show ddl for non-default schema when logged in as sysdba (administrator). </li><li>Show ddl command now works for a table with an autoincrement column. </li><li>An exception is reported when there are two tables with foreign keys that reference each other, and both tables are being updated by separate transactions a lock timeout error can occur. This has been fixed. </li><li>Wrong result from running join query has been fixed. </li></ul> <h3><a name="fixed_701">Bugs Fixed in 7.01</a></h3><ul><li>Modify output of date and time to include at least 2 digits for day, month, minute, second, hours. </li><li>Remote JDBC driver improved server exception handling. </li><li>A prepared query with a parameterized LIKE operator in the where clause e.g. "SELECT * FROM PERSON WHERE LASTNAME LIKE ?"was mistakenly executed with the parameter given first time the query was executed; thus subsequent executions would receive wrong results. This problem has been fixed. </li><li>A SQL query which uses an auto-increment field for a lookup or join may in certain circumstances yield the wrong result. This problem has been fixed. </li><li>Tables with a column named INTERNALROW, could not be exported using ISQL. This problem has been fixed. </li><li>The data presented in the ServerConsole and the SQL tab in JdsExplorer for a query like: "SELECT * FROM MY_VIEW" could not be edited even if the view was updateable. This problem has been fixed. </li><li>TxException LOCK_TIMEOUT errors fixed for situations where table lock escalation is triggered to max row locks exceeded. </li><li>Problem when value from source cursor had a maxInline setting that was larger than the destination cursor. Cursor now can convert inline into blob if necessary. </li><li>Drop column no longer fails to have any affect if another connection has a prepared statement that references the same table. </li><li>The command SHOW TABLE in ISQL required an explicit schema name. This problem has been fixed. </li><li>Cannot drop primary mirror. Problem is now fixed. </li> <li>ResultSetMetaData now returns the correct column count when an updateable ResultSet is used. </li><li>Column from Primary keys were sometimes reported to be nullable through DatabaseMetadata.getColumns().This problem has been fixed. </li><li>If 2 timestamp values are given as 2 literals the first value is stored for both values. This problem has been fixed. </li><li>The Date and Timestamp literal JDBC escape formats were incorrectly documented. This problem has been fixed. </li></ul> http://cc.embarcadero.com/Item/25371 2008-05-13T22:17:59 2008-05-13T22:17:59 http://cc.embarcadero.com/Item/25371 <h1 align="center"><a name="_top_"></a>JDataStore 7.06 (build 7.006.039) for Linux<br>Release Notes</h1><p>These Release Notes provide a brief description of each new feature in JDataStore 7.The <cite>JDataStore Developer's Guide</cite> includes a "What's New" chapter that provideslinks to the documentation for each new feature within the Developer's Guide.</p><p><strong>Bug fix list</strong></p><ul><li>To see bugs fixed in JDataStore 7.06 click <a href="#fixed_706">here</a></li><li>To see bugs fixed in JDataStore 7.05 click <a href="#fixed_705">here</a></li><li>To see bugs fixed in JDataStore 7.04 click <a href="#fixed_704">here</a></li><li>To see bugs fixed in JDataStore 7.03 click <a href="#fixed_703">here</a></li><li>To see bugs fixed in JDataStore 7.02 click <a href="#fixed_702">here</a></li><li>To see bugs fixed in JDataStore 7.01 click <a href="#fixed_701">here</a></li></ul><p><strong>New Features</strong></p><ul><li><a href="#failsafe">The JDataStore High Availability Server: incremental backup, automatic failover</a></li><li>The new <a href="#console">Server Console</a> graphical interface</li></ul><p><strong>New SQL functions</strong></p><ul><li><a href="#bit_length"><code>BIT_LENGTH</code></a></li><li><a href="#case_function"><code>CASE</code></a></li><li><a href="#coalesce"><code>COALESCE</code></a></li><li><a href="#current_role"><code>CURRENT_ROLE</code></a></li><li><a href="#current_user"><code>CURRENT_USER</code></a></li><li><a href="#db_admin"><code>DB_ADMIN</code></a></li><li><a href="#DB_UTIL"><code>DB_UTIL</code></a></li><li><a href="#nullif"><code>NULLIF</code></a></li><li><a href="#octet_length"><code>OCTET_LENGTH</code></a></li><li><a href="#user_function"><code>USER</code></a></ul><p><strong>New and updated SQL statements</strong></p><ul><li><a href="#create_schema"><code>CREATE SCHEMA</code></a>, <a href="#drop_schema"><code>DROP SCHEMA</code></a></li><li><a href="#create_view"><code>CREATE VIEW</code></a>, <a href="#alter_view"><code>ALTER VIEW</code></a>, <a href="#drop_view"><code>DROP VIEW</code></a></li><li><a href="#create_role"><code>CREATE ROLE</code></a>, <a href="#set_role"><code>SET ROLE</code></a>, <a href="#drop_role"><code>DROP ROLE</code></a></li><li>New <code><a href="#create_table">CREATE TABLE</a></code> options</li><li>New <code><a href="#alter_table">ALTER TABLE</a></code> options</li><li>New <code><a href="#drop_table">DROP TABLE</a></code> options: <code>CASCADE</code> and <code>RESTRICT</code></li><li><a href="#create_java_class"><code>CREATE JAVA_CLASS</code></a>, <code><a href="#drop_java_class">DROP JAVA_CLASS</a></code></li></ul><p><strong>Security management</strong></p><ul><li><code><a href="#grant_statement">GRANT</a></code> and <code><a href="#revoke_statement">REVOKE</a></code></li><li><code><a href="#create_user">CREATE USER</a></code>, <code><a href="#alter_user">ALTER USER</a></code>, <code><a href="#drop_user">DROP USER</a></code></li></ul><p><strong>Transaction management</strong></p><ul><li><code><a href="#set_transaction">SET TRANSACTION</a></code></ul><p><strong>Other new SQL</strong></p><ul><li><a href="#keywords">New keywords</a></li><li>New data type: <a href="#tinyint"><code>TINYINT</code></a></li><li>Many new <a href="#escape_functions">JDBC escape functions</a></li><li><a href="#isql">ISQL cross-platform SQL command-line utility</a></li></ul><p><strong>Product notes</strong></p><ul><li><a href="#choose">Choosing between Server Console and JdsExplorer</a></li><li><a href="#change_copy">A change to the "Copy JDataStore" menu item</a></li></ul><p><strong>New and updated documentation</strong></p><ul><li><a href="#new_chaps">New chapters</a></li><li><a href="#escape">Escape syntax for calling stored procedures</a> is now documented.</li><li>Updated documentation on <a href="#jdbc_resultset">returning JDBC ResultSets</a></li></ul><p><strong>Getting started with JDataStore 7</strong></p><ul><li><a href="#migration">Migrating older databases to JDataStore 7</a></li><li><a href="#jb_bes">Using JDataStore 7 with JBuilder and the Borland Enterprise server</a></li></ul><!-- <p><a href="#bugs">Defects fixed in JDataStore 7</a></p> --><!-- <h2><a name="features"></a>New features</h2> --><h2><a name="features"></a>New features</h2><h3><a name="failsafe"></a>The JDataStore High Availability Server</h3><p>JDataStore 7 provides tools for creating automatic or manual incremental backups and for creating automatic failover to a mirror of the original database in case of failure. In addition, there are tools for viewing and managing connections on a remote server, for managing datasources and connections graphically or with the new ISQL feature, for viewing database status logs and transactions logs, for viewing logs, and for verifying databases.</p><p>The "High Availability Server" topic in the "Architecture" chapter of the <cite>JDataStore Developer's Guide</cite> discusses the architecture of JDataStore's new failsafe server and its associated mirroring functionality. This section is well worth reading, because it will help you make the most of this new offerings. </p><p>For a description of how to use JDataStore's new Server Console to access this new functionality, see the new "JDataStore Server Console" chapter in the <cite>JDataStore Developer's Guide</cite>. </p> <h3><a name="console"></a>The new Server Console graphical interface</h3><p>There is a whole new graphical interface in JDataStore 7. The Server Console performs many server administration tasks, including several that are new in JDataStore 7, such as automatic failover and incremental backup.</p><p>Here is an overview of what you can do with the Server Console. The items in the following list are topics in the "JDataStore Server Console" chapter of the <cite>JDataStore Developer's Guide</cite> for details.</p><ul><li><strong>Overview</strong> Get a quick overview of what you can do with Server Console</li><li><strong>About datasources</strong> If you're not familiar with how JDataStore uses dataasources to connect to databases, this is the place to find out.</li><li><strong>What you see and what you get</strong> Get familiar with the new Server Console interface.</li><li><strong>Starting/shutting down the server</strong> You can use Server Console to start and stop the local server.</li><li><strong>Connection settings</strong> A detailed description of how to create, modify, and delete datasources, and how to connect to and disconnect from them.</li><li><strong>Creating and managing datasources</strong> Create, rename, and modify datasources, connect to them, and disconnect from them.</li><li><strong>Verifying a database</strong> Server Console makes it easier than ever.</li><li><strong>Managing connections</strong> View and optionaly terminate both local and remote datasources.</li><li><strong>Managing database properties</strong> See an editable grid of database properties for both local and remote connections.</li><li><strong>Viewing table and row locks</strong> Server Console makes it easy to see what's happening with locks on both the local and remote server.</li><li><strong>Viewing the database status log file</strong> You exactly what's been going on with a server by viewing its server status file.</li><li><strong>Failover</strong> and <strong>incremental backup</strong> Use mirrors to protect against failures and to incrementally backup your data on a schedule of your choosing. Using Server Console, you can add </li><li><strong>Interactive SQL</strong> A special SQL pane lets you run SQL or SQL scripts against connected datasources.</li></ul><p><strong>What happened to the old JdsServer graphical interface?</strong> It's still there, but it has been replaced by the new Server Console. You can still start the JDataStore server as an application by running the <code>JdsServer</code> executable. However, it is now set to run without the GUI. If you really need that deprecated interface back, you can invoke the GUI by executing the following command:</p><table class="pre"><tr><td><pre>jdsserver -ui [windows|motif|metal|none][other parameters]</pre></td></tr></table><p>Choose the interface that is appropriate for your platform. For more about starting the JDataStore server, see "Launching JdsServer" in the "JDataStore Administration" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="keywords"></a>New keywords</h3><p>The asterisk following a keyword indicates that the keyword is <em>reserved</em>. Reserved keywords can be used as SQL identifiers only if they are enclosed in double quotation marks. When quoted in this fashion, they are case sensitive. The words that have no asterisk are <em>nonreserved</em> keywords. They can be used with or without double quotes and are case insensitive when note in quotes.</p><p>For a complete list of keywords, see <strong>Keywords</strong> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><table border="0"><tr><td>ADMIN*<br>ADMINISTRATOR*<br>AUTHORIZATION*<br>BIT_LENGTH*<br>COALESCE*<br>CURRENT_ROLE*<br>CURRENT_USER*<br>EXECUTE*<br>GRANT*<br>ISOLATION*<br></td><td>LEVEL*<br>NONE*<br>NULLIF*<br>OCTET_LENGTH*<br>ONLY*<br>OPTION*<br>PRIVILEGES*<br>PUBLIC*<br>READ<br>RENAME*<br></td><td>RESOLVABLE*<br>REVOKE*<br>ROLE<br>SCHEMA*<br>STARTUP*<br>TO*<br>TRANSACTION*<br>VIEW*<br>WITH*<br>WRITE<br></td></tr></table> <h2><a name="new_funcs"></a>New SQL functions</h2><h3><a name="bit_length"></a>BIT_LENGTH</h3><p>The <code>BIT_LENGTH</code> function gives the length in bits of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>BIT_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="case_function"></a>CASE</h3><!--BNDX="CASE function;SQL functions:CASE"--><p>The <code>CASE</code> function returns a conditional value. For more information, see <code>CASE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="coalesce"></a>COALESCE</h3><!--BNDX="COALESCE function;SQL functions:COALESCE;non-NULL values, returning"--><p>The <code>COALESCE</code> function returns the first non-NULL value from the expression list. For more information, see <code>COALESCE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="current_role">CURRENT_ROLE</a></h3><!--BNDX="CURRENT_ROLE function;SQL functions:CURRENT_ROLE;roles"--><p>The <code>CURRENT_ROLE</code> function returns the current role, or NULL if no role has been set using the <code>SET ROLE</code> statement. For more information, see <code>CURRENT_ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. </p><h3><a name="current_user"></a>CURRENT_USER</h3><!--BNDX="CURRENT_USER function;SQL functions:CURRENT_USER"--><p>The <code>CURRENT_USER</code> function returns the name of the current user. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="db_admin"></a>DB_ADMIN: administration functions</h3><!--BNDX="DB_ADMIN function;SQL functions:DB_ADMIN"--><p><code>DB_ADMIN</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. Use <code>DB_ADMIN</code> for various database administration tasks such as automatic failover, incremental backup, creating and managing datasources, viewing and managing connections, verifying tables, and displaying database privileges and properties, locks, status logs, procedure privileges, and roles granted.</p><p><code>DB_ADMIN</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method, implemented as a SQL function. The description of each method includes a link to the exact implementation and <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_ADMIN</code> provides the following methods:</p><table border="0" cols="3"><tr><td><code>ALTER_DATABASE<br>ALTER_MIRROR<br>ALTER_MIRROR_SCHEDULE<br>CLOSE_CONNECTION<br>CREATE_MIRROR<br>CREATE_MIRROR_SCHEDULE<br>DROP_MIRROR<br>DROP_MIRROR_SCHEDULE<br>GET_CONNECTIONS<br>GET_DATABASE_PRIVILEGES<br>GET_DATABASE_PROPS<br>GET_DATABASE_STATUS_LOG_FILTER<br>GET_LOCKS</code></td><td><code>GET_MIRRORS<br>GET_NEWEST_STATUS_LOG_ID<br>GET_OLDEST_STATUS_LOG_ID<br>GET_PROCEDURE_PRIVILEGES<br>GET_ROLE_GRANTS<br>GET_STATUS_LOG_FILTER<br>GET_STATUS_LOG<br>GET_THIS_MIRROR<br>SET_DATABASE_STATUS_LOG_FILTER<br>SET_PRIMARY_MIRROR<br>SET_STATUS_LOG_FILTER<br>SYNCH_MIRROR<br>VERIFY</code> </td></tr></table> <br> <h3><a name="DB_UTIL"></a>DB_UTIL: numeric, string, and date/time functions</h3><!--BNDX="DB_UTIL functions;SQL functions:DB_UTIL;math functions;string functions;date/time functions;utilities:DB_UTIL"--><p><code>DB_UTIL</code> is a new JDataStore Java class whose methods are implemented in SQL as built-in stored procedures. They are a collection of SQL utility functions that perform numeric, string and date/time operations on data stored in database tables. </p><p><code>DB_UTIL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> provides a brief description of each method. The description of each method includes a link to the exact implementation in <a href="../apiref/com/borland/datastore/driver/DB_ADMIN.html#method_summary"><code>com.borland.datastore.driver.DB_ADMIN.html</code></a> in the API reference. (The preceding link works when this document is in the <code><em>JDataStore_home</em>\doc</code> directory.) </p><p>You can call these methods from SQL using the <code>CALL</code> statement. They can be called without creating a <code>JAVA_METHOD</code> alias because JDataStore SQL recognizes the methods in <code>DB_ADMIN</code> as built-in java methods.</p><p><code>DB_UTIL</code> provides the following methods</p><table border="0"><tr><td><code><br>ACOS<br>ASIN<br>ATAN<br>ATAN2<br>CEILING<br>COS<br>COT<br>DEGREES<br>EXP<br>FLOOR<br>LOG<br>LOG10<br>MOD<br>PI</code></td><td><br><code>POWER<br>RADIANS<br>RAND<br>ROUND<br>SIGN<br>SIN<br>SQRT<br>TAN<br>TRUNCATE<br>ASCII<br>TO_CHAR<br>DIFFERENCE<br>INSERT_STRING<br>LEFT_STRING</code></td><td><code><br>REPEAT<br>REPLACE<br>RIGHT<br>SOUNDEX<br>SPACE<br>DAYNAME<br>DAYOFWEEK<br>DAYOFYEAR<br>MONTHNAME<br>QUARTER<br>TIMESTAMPADD<br>TIMESTAMPDIFF<br>WEEK</code></td></tr></table> <br> <h3><a name="nullif"></a>NULLIF</h3><!--BNDX="NULLIF function;SQL functions:NULLIF;expressions:comparing;comparisons:expressions with NULLIF"--><p>The <code>NULLIF</code> function compares two expressions. It returns NULL if the expressions are equal. Otherwise, it returns the first expression. It is logically equivalent to the following <code>CASE</code> expression: <code>CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END</code><br><br>For more information, see <code>NULLIF</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="octet_length"></a>OCTET_LENGTH</h3><!--BNDX="OCTET_LENGTH function;SQL functions:OCTET_LENGTH;length of string, imput stream, or object"--><p>The <code>OCTET_LENGTH</code> function gives the length in bytes of a <code>STRING</code>, <code>INPUTSTREAM</code>, or <code>OBJECT</code> value. For more information, see <code>OCTET_LENGTH</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="user_function"></a>USER</h3><!--BNDX="USER function;SQL functions:USER"--><p>The <code>USER</code> function returns the name of the current user; this function is the same as <code><a href="#current_user">CURRENT_USER</a></code>. For more information, see <code>CURRENT_USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="new_sql"></a>New and updated SQL statements</h2><h3><a name="create_schema"></a>CREATE SCHEMA</h3><!--BNDX="CREATE SCHEMA statement;schemas:creating;SQL statements:CREATE SCHEMA"--><!--BNDX="statements, <em>see</em> SQL statements"--><p>The <code>CREATE SCHEMA</code> statement creates a name space for tables, views, and methods. You can use <code>CREATE SCHEMA</code> to create multiple objects in one SQL statement. For a discussion of how schemas work in JDataStore, see <code>CREATE SCHEMA</code> and <code>DROP SCHEMA</code>in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_schema"></a>DROP SCHEMA</h3><!--BNDX="DROP SCHEMA statement;schemas:dropping;SQL statements:DROP SCHEMA"--><p>The <code>DROP SCHEMA</code> statement deletes the specified schema. If the command is used without options, it is the same as specifying the <code>RESTRICT</code> option: the schema to be dropped must be empty. The command fails if the schema contains any objects. </p> <p class="bscan"><span class="bscan">Note: </span>The <code>DROP SCHEMA</code> command used with the <code>CASCADE</code> option is extremely powerful and should be used with caution. When this command is issued, it drops the schema and all of its objects and dependencies without any chance to change your mind. There is no undo.</p> <h3><a name="create_view"></a>CREATE VIEW</h3><!--BNDX="CREATE VIEW statement;SQL statements:CREATE VIEW;views:creating"--><p>The <code>CREATE VIEW</code> statement creates a derived table by selecting specified columns from existing tables. Views provide a way of accessing a consistent subcollection of the data stored in one or more tables. When the data in the underlying tables changes, the view reflects this change.</p>For more information, see <code>CREATE VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="alter_view"></a>ALTER VIEW</h3><!--BNDX="ALTER VIEW statement;SQL statements:ALTER VIEW;views:altering"--><p>The <code>ALTER VIEW</code> statement modifies a view without losing dependent views and existing <code>GRANT</code>s. This statement can be used to change the name of a view, the columns that comprise the view, and whether the view has the <code>WITH CHECK OPTION</code> constraint. For more information, see <code>ALTER VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_view"></a>DROP VIEW</h3><!--BNDX="DROP VIEW statement;SQL statements:DROP VIEW;views:dropping"--><p>The <code>DROP VIEW</code> statement drops the named view. By default, it fails if there are dependencies on the view. The <code>CASCADE</code> option drops the view and any dependent views. For more information, see <code>DROP VIEW</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_role"></a>CREATE ROLE</h3><!--BNDX="CREATE ROLE statement;SQL statements:CREATE ROLE;roles:creating;privileges:roles"--><p>The <code>CREATE ROLE</code> statement creates a named role. To complete this functionality, you must <code>GRANT</code> privileges to the role, and <code>GRANT</code> the role to one or more users. To make use of the privileges acquired in this fashion, the user issues a <code>SET ROLE</code> statement.</p><p>For more information, see <code>CREATE ROLE</code> and the <code>GRANT</code> statement in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="set_role"></a>SET ROLE</h3><!--BNDX="SET ROLE statement;SQL statements:SET ROLE;roles:activating;privileges:roles"--><p>The <code>SET ROLE</code> statement makes the named role active. The current user acquires all privileges assigned to that role. For more information, see <code>SET ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_role"></a>DROP ROLE</h3><!--BNDX="DROP ROLE statement;SQL statements:DROP ROLE;roles:dropping"--><p>The <code>DROP ROLE</code> statement drops the specified role. For more information, see <code>DROP ROLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_table"></a>CREATE TABLE</h3><!--BNDX="CREATE TABLE statement;JDataStore tables:creating;foreign keys;SQL statements:CREATE TABLE"--><!--BNDX="schemas:creating tables in;JDataStore tables:schemas"--><p>There are three new options for the <code>CREATE TABLE</code> statement:</p><ul><li>The table name now incldues a schema name.</li><li>You have the option of specifying a position for each column.</li><li>You can use the [NOT] RESOLVABLE option to track data changes for DataExpress.</li></ul><p>For more information, see <code>CREATE TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_table"></a>ALTER TABLE</h3><!--BNDX="ALTER TABLE statement;JDataStore tables:modifying;SQL statements:ALTER TABLE"--><p>There are several new options for the <code>ALTER TABLE</code> statement:</p><ul><li>You can rename the entire table; this is how you assign a table to a different schema.</li><li>You can make the table <code>RESOLVABLE</code> or <code>NOT RESOLVABLE</code>.</li><li>At the column level you can:<ul><li>Change the datatype of a column</li><li>Set whether a collumn is nullable</li><li>Rename a column</li><li>Change the position of a column within the table</li></ul></li></ul><p>For more information, see <code>ALTER TABLE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_table"></a>DROP TABLE</h3><!--BNDX="DROP TABLE statement;SQL statements:DROP TABLE;JDataStore tables:deleting"--><p>The <code>DROP TABLE</code> statement deletes a table and its indexes from a JDataStore database. <code>DROP TABLE</code> has two new options: <code>RESTRICT</code> and <code>CASCADE</code>.</p> <h3><a name="create_java_class"></a>CREATE JAVA_CLASS</h3><!--BNDX="CREATE JAVA_CLASS statement;SQL statements:CREATE JAVA_CLASS;Java classes:creating;creating:java classes"--> <p>The <code>CREATE JAVA_CLASS</code> statement makes all public static methods of a Java class available to JDataStore SQL as stored procedures or UDFs. For more information, see <code>CREATE JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="drop_java_class"></a>DROP JAVA_CLASS</h3><!--BNDX="DROP JAVA_CLASS statement;SQL statements:DROP JAVA_CLASS;Java classes:dropping;dropping:java classes"--> <p>The <code>DROP JAVA_CLASS</code> statement drops a stored class, making it unavailable for use in JDataStore SQL. For more information, see <code>DROP JAVA_CLASS</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="grant_statement"></a>GRANT</h3><!--BNDX="GRANT statement;SQL statements:GRANT;database privileges, granting;privileges:granting;roles:granting privileges to;roles:granting to users"--><p>The <code>GRANT</code> statement performs the following actions:</p><ul><li>It grants object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods to <code>PUBLIC</code>, users, or roles.</li><li>It grants database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—to users or roles.</li><li>It grants roles to users or roles.</li></ul>For more information, see <code>GRANT</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.<h3><a name="revoke_statement"></a>REVOKE</h3><!--BNDX="REVOKE statement;SQL statements:REVOKE;database privileges, revoking;roles:revoking privileges"--><p>The <code>REVOKE</code> statement performs a number of actions:</p><ul><li>It revokes object privileges—such as <code>INSERT</code> or <code>SELECT</code>—on tables or java methods from <code>PUBLIC</code>, users, or roles. It has <code>CASCADE</code> and <code>RESTRICT</code>,options.</li><li>It revokes database privileges—such as <code>STARTUP</code> or <code>RENAME</code>—from users or roles.</li><li>It revokes roles from users or roles.</li><li>It revokes the <code>ADMIN</code> option from a role without revoking the role itself.</li><li>It revokes the <code>GRANT</code> option from a privilege without revoking the privilege itself.</li></ul><p>For more information, see <code>REVOKE</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="create_user"></a>CREATE USER</h3><!--BNDX="CREATE USER statement;SQL statements:CREATE USER;users:adding with CREATE USER"--><p>The <code>CREATE USER</code> statement adds the named user and associated password to the database. The password is case sensitive, the user name is not. For more information, see <code>CREATE USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="alter_user"></a>ALTER USER</h3><!--BNDX="ALTER USER statement;SQL statements:ALTER USER;users:editing with ALTER USER"--><p>The <code>ALTER USER</code> statement sets a new password for an existing user. For more information, see <code>ALTER USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="drop_user"></a>DROP USER</h3><!--BNDX="DROP USER statement;SQL statements:DROP USER;users:removing with DROP USER"--><p>The <code>DROP USER</code> statement drops a user and all objects that the user owns. It has <code>RESTRICT</code> and <code>CASCADE</code> options. For more information, see <code>DROP USER</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h3><a name="set_transaction"></a>SET TRANSACTION</h3><!--BNDX="SET TRANSACTION statement;SQL statements:SET TRANSACTION;transactions: setting; transaction isolation levels, overview;isolation levels:setting"--><p>The <code>SET TRANSACTION</code> statement sets the properties for the following transaction. You can use it to specify the isolation level and whether the transaction is read-write or read-only. For more information, see <code>SET TRANSACTION</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>. See <a href="architecture.html#tx_management">"Transaction management"</a> in the "System Architecture" chapter for further discussion of JDataStore transaction management.</p><h3><a name="tinyint"></a>New data type: TINYINT</h3><p>JDataStore SQL now provides a one-byte integer data type, <code>TINYINT</code> (or <code>BYTE</code>). For more information, see "Datatypes" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="escape_functions"></a>JDBC escape functions</h3><!--BNDX="JDBC escape functions;SQL functions:JDBC escape functions;functions:JDBC escape functions"--><p>JDataStore now provides a greatly expanded list of JDBC escape functions. For a complete list, see "JDBC escape functions" the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="isql"></a>ISQL</h3><p>JDataStore's new ISQL can be run in the SQL tab of the Server Console. These commands can also be issued from any system command console.</p><p>For a discussion of JDataStore new ISQL and a list of commands, see <code>ISQL</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="notes"></a>Product notes</h2><h3><a name="choose"></a>Choosing between JdsExplorer and the Server Console</h3><p>The Server Console is a graphical interface that is new in JDataStore 7. In it, you can perform some of the tasks that you previously performed in JdsExplorer. In addition, Server Console provides access to many new features.</p><p>From Server Console you can:</p><ul><li>Create and edit datasources, connect to local or remote databases, and view and manage connections. </li><li>View and manage database properties, and view database status logs, view table and row locks. and verify databases. You cannot create databases in Server Console.</li><li>Create and manage mirrors for incremental backup, auto failover, and load balancing.</li><li>Use the ISQL tab to execute all SQL and ISQL commands. There is a list of ISQL commands at the end of the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite>. JdsExplorer off an environment for executing SQL commands, but you cannot execute ISQL commands there.</li></ul><p>You need JdsExplorer if you want to:</p><ul><li>Perform user administration</li><li>Manage license keys</li><li>Work with and view table structure and content, including indexes.</li><li>Import tables from other databases and import text and images into a database</li><li>Upgrade, downgrade, copy, encrypt/decrypt or pack a database. Database verification can be performed from either JdsExplorer or Server Console.</li></ul><p>Most of the tasks listed for JdsExplorer can be performed in the Server Console using the ISQL window.</p><h3><a name="change_copy"></a>A change to the "Copy JDataStore" menu item</h3><p>JdsExplorer has a Copy JDataStore item on the Tools menu. Its function is different in JDataStore 7 then in earlier versions of the product. In previous versions of JDataStore, choosing Tools|Copy JDataStore brought up the Copy Streams dialog box, and made you select exactly which streams to copy. Now this menu item brings up a dialog in which you copy an entire database file.</p><p>There is a new item on the JDataStore Tools menu: Copy Into Existing JDataStore. This item permits you to copy into an existing, empty JDataStore, which allows you to downgrade or encrypt databases.</p><p>To copy individual tables between databases, use the Tools|Import chose in JdsExplorer.</p> <h2><a name="new_doc"></a>New and updated documentation</h2><h3><a name="new_chaps"></a>New chapters</h3><p>There are two new chapters in the <cite>JDataStore Developer's Guide</cite>. </p><ul><li>The "What's New" chapter lists the new features and provides links into those topics in the book.</li><li>The "JDataStore Server Console" chapter provides details about the new Server Console interface and the things you can do with it.</li></ul><h3><a name="exapnd_sql"></a>Expanded SQL Reference</h3><p>The JDataStore implementation of the SQL language has been greatly enriched, and the SQL Reference chapter in the <cite>JDataStore Developer's Guide</cite> has been expanded and reorganized.</p><h3><a name="escape"></a>JDBC escape syntax</h3><!--BNDX="JDBC escape sequences;JDataStore tables:string functions;JDataStore tables:JDBC escape sequences;literals in JDBC escape sequences"--><p>The JDBC escape syntax was not previously documented. It is now in the "JDBC escape syntax" in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jdbc_resultset"></a>Stored procedures and JDBC ResultSets</h3><!--BNDX="JDBC result set;result set, JDBC;returning a JDBC result set"--><!--BNDX="JDBC DataSets;DataSets, returning"--><p>A Java stored procedure can produce a <code>ResultSet</code> on the client by returning either a <code>ResultSet</code> or a DataExpress <code>DataSet</code> from the Java implementation of the stored procedure. The <code>DataSet</code> is automatically converted to a <code>ResultSet</code> for the user of the stored procedure.</p><p>Documentation on the feature has been expanded in JDataStore 7. For more information, see "Stored procedures and JDBC ResultSets" in the "Stored Procedures and UDFs" chapter of the <cite>JDataStore Developer's Guide</cite>.</p> <h2><a name="start"></a>Getting started with JDataStore 7</h2><h3><a name="migration"></a>Migrating older databases to JDataStore 7</h3><p>The big issue in migrating older databases to JDataStore 7 is that JdataStore 7 has the concept of schemas, and older databases do not. In JDataStore 7, every table belongs to a schema: the schema name is part of the table name. In general, when a user creates an object such as a table or a view, that object belongs to the user's own schema. There are a number of issues regarding the use of schemas. It will be helpful to you to read <code>CREATE SCHEMA</code> in the "SQL Reference" chapter of the <cite>JDataStore Developer's Guide</cite> to understand how JDataStore 7 uses schemas before proceeding with migration.</p><p>For additional detail on migrating older JDataStore databases to JDataStore 7, see "Migrating older databases to JDataStore 7" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><h3><a name="jb_bes"></a><strong>Using JDataStore 7 with JBuilder and the Borland Enterprise Server</strong></h3><p>To make the latest version of JDataStore available to JBuilder and the Borland Enterprise Server (BES), you need to copy certain files form the JDataStore <em>lib</em> directory to the <em>lib</em> directory of the target product. The files are: <em>beandt.jar</em>, <em>dbtools.jar</em>, <em>dx.jar</em>, <em>jds.jar</em>, <em>jdsremote.jar</em>, and <em>jdsserver.jar</em></p><p>For more information, see "Using JDataStore with JBuilder and the Borland Enterprise server" in the "JDBC Quickstart" chapter of the <cite>JDataStore Developer's Guide</cite>.</p><p>Field test note: For the field test, copying these files may cause some menu problems in JBuilder. These problems go away when you remove the copied files. This defect will be fixed for the final release.</p><h2>Change listing for each point release.</h2><h3><a name="fixed_706">Bugs Fixed in 7.06</a></h3><ul><li>Mac installer has been replaced with an installer for intel Mac platform. PowerPC mac's are no longer supported.</li></ul><ul><li>Certain prepared queries with aggregators resulted in bad data.</li></ul><ul><li>Certain prepared queries with an IN operator resulted in a sporadic NullPointer exception. Safeguards have been added.</li><li>If a range is specified in the WHERE clause for an autoincrement column, the wrong rows might be returned. This is also true for certain primary key columns that implicitly are converted into auto increment columns.</li><li>JDataStore 7.006 has been certified for Microsoft Vista. We recommend that the developer edition of JDataStore be installed outside of the “Program Files” directory. The JDataStore .exe launchers depend on config files that are located in the same directory as the launcher.exe. If the product is installed in the “Program Files” directory and Vista UAC is enabled, the changes to the config files will only take affect for the user that makes the modifications. Note that this is mostly of concern to developers or server side installations that use one of the exe launchers. These are the exe Launchers installed by the developer edition of JDataStore: JdsServer*.exe, isql.exe, JdsExplorer*.exe, and ServerConsole*.exe. Note that there are no issues for installing JDataStore jar files in the “Program Files” directory.</li><li>Data corruption from sql update statements under high concurrency environments has been fixed.<li></li>Thread deadlock in JdbcConnectionPool shutdown method that occurs when another thread is also returning a connection to the pool by calling java.sql.Connection.close method has been fixed.</li><li>ArrayIndexOutOfBoundsException that occurs for descending sort operations on String columns</li><li>Prepared statement with grouping criteria may produce incorrect results the second time it is executed when other statements that use the same table are prepared and executed.</li><li>Joins with range selection criteria for more than one table on columns with the same ordinal position can encounter value access errors indicating a type mismatch.</li><li>DB_ADMIN.GET_CONNECTIONS() built in stored procedure will now include local connections in addition to remote connections. This includes connections open with the DataStoreConnection and DataStore components. Connections with a "USER" column that starts with "sys." and connections that have a "REMARKS" column value of "Opener" are internal connections that do not keep a database from shutting down.</li> <h3><a name="fixed_705">Bugs Fixed in 7.05</a></h3><ul><li>An UPDATE query which uses an aggregation of a subquery with an outer reference to set a column value could cause a NullPointerException.</li><li>DatabaseMetaData.getIndexInfo() returned wrong information about auto increment columns.</li><li>A combination of a 1-1 query of 2 tables with single integer column primary keys and an IN operator in the WHERE clause could cause an Exception.</li><li>Creating a table with a single integer column primary key and a different column as an auto increment column, will cause the auto increment column to not function.</li><li>Applications that close connections without closing open statements will incur a memory leak if the statements had executed queries that return ResultSets.</li><li>SQL queries with an “in clause” selection criteria that references an indexed column may not return all rows that satisfy the in clause selection criteria.</li><li>Table open and close operations can fail if several connections are rapidly opening and closing connections. This can also cause connection close operations to fail resulting in "lingering" connections in the DataStoreServer.</li><li>Statement caching provided by the connection pool does not properly cache or close statements. Because resources and ResultSets are not closed until these unclosed statements are finalized, this can lead to out of memory conditions and large temporary database file sizes.</li><li>For encrypted databases, the crash recovery system can encrypt modified blocks of the user table. This is a mistake because the user table is the one table that cannot be encrypted in an encrypted database. Note that this will only occur if some change is made to the user table since the last time the database was opened. This problem can prevent the database from being opened or cause the user table to appear corrupt when database verification is performed. We are working on a repair method for applications that have encountered this problem.</li><li>Support for opening encrypted databases that have part or all of the user table encrypted by the defect described above. If the user table record for the user connecting is encrypted, the database cannot be opened. In this case there is a new connection property called "priorFileName" that can be used to provide the name of a prior version of the encrypted database that can still be opened. This can be specified as an extended JDBC property for JDBC connections. There is also a DataStoreConnection.setPriorFileName as well. Note that the prior database will only be used to unencrypt the user table that is not supposed to be encrypted in the first place. If the user logging in does not have startup rights in both the prior and current database, the prior database will not be used for the open operation. Once the database affected by this defect has been opened, it should be copied or packed into a new database file.</li></ul> <h3><a name="fixed_704">Bugs Fixed in 7.04</a></h3><ul><li>When "Tools | Encrypt JDataStore" or "Tools | Copy JDataStore" is selected from JdsExplorer, the resulting database has multiple entries for the SYSDBA user. This problem has been fixed.</li><li>When combining an "order by" and an "in" and a sub select on a large set of records, it may result in an incorrect record count.</li></ul> <h3><a name="fixed_703">Bugs Fixed in 7.03</a></h3><h4>Support for Hibernate</h4><ul><li>Hibernate's automated test suites completed. Hibernate dialect class provided in samples directory.</li></ul><h4>General defect corrections and improvements</h4><ul><li>ADMINISTRATOR is now a non reserved keyword in SQL. (It used to be a reserved keyword.)</li><li>Corrected defect in remote driver where retrieving longer string or blob values sometimes caused the driver to hang. </li><li>Database check point events are now logged in the *STATUS * log files. These messages provide "remarks" on what is keeping a log file from being dropped. This can be useful when trying to diagnose why log files are not being automatically dropped. </li><li>New ExtendedProperties.REMARKS property. This can be set to an informative string. This is displayed in many of the contexts in which user name is displayed. Many applications use the same user for many connections. The remarks property makes it easier to distinguish connections that use the same user name. Remarks is displayed for lock error reporting, DB_ADMIN.GET_CONNECTIONS() builtin stored procedure and the connections node of the ServerConsole. </li></ul><h4>SMP support</h4><ul><li>Completion of all automated stress tests on dual processor Windows XP and Redhat Enterprise Linux 3. </li></ul><h4>High availability corrected defects and improvements</h4><ul><li>General stability improvements. </li><li>Improved performance for mirror synchronization. </li><li>Eliminated problems where log files would never drop for databases with mirrors in certain situations. </li><li>Mirrors with the INSTANT_SYNCH or AUTO_FAIL_OVER property set will automatically have a mirror schedule item added to the SYS.MIRROR_SCHEDULE table. This mirror schedule item is added when the mirror is created or when the INSTANT_SYNCH or AUTO_FAIL_OVER property is altered for a mirror that does not already have a mirror schedule item. This default mirror schedule item will synchronize the mirror every 10 seconds. This mirror schedule item can be dropped or altered after the mirror is created if so desired. However, it is probably best to keep a mirror schedule item for each mirror so that the read only mirror database is kept up to date with the primary mirror. When INSTANT_SYNCH or the AUTO_FAIL_OVER property is set for a read only mirror its log records are constantly kept in synch with the primary mirror. However, these log records are not replayed against the read only mirror database until a synch operation is performed. The mirror schedule item will synch the mirror on a regular basis keeping the state of the read only mirror database very close or equal to the state of the primary mirror. Two key benefits of having the readonly mirror databases up to date with the primary mirror are: 1) Fail over (manual or automatic) is much faster because little or no log records need to be replayed before the fail over operation. 2) Readonly mirror databases will reflect a more recent state of the database. This will be important for applications that off load readonly queries from the primary mirror to readonly mirrors. </li><li>ISQL show ddl command now outputs the sql call statements to recreate any mirrors configured for the database. This is useful to see how mirrors are can be created from executing a sql script. </li><li>The last known replay column for the mirrors table and mirror status table in the ServerConsole now displays these values in hex. The high 32 bits are the log file and the low 32 bits are the offset into the log files. These values determine when log files can be automatically dropped. For example a primary mirror cannot drop a log if a read only mirror has not replayed the contents of that log file. So if the last known replay for a read only mirror as a low log file for its last replay column, this will keep this log file and all log files greater than this log file from being dropped. </li></ul> <h3><a name="fixed_702">Bugs Fixed in 7.02</a></h3><ul><li>There have been many significant improvements in High availability Mirrors as well as Read-Only Transactions. </li><li>Mirroring support now drops unneeded log files when it should. </li><li>Cannot use export or show ddl command when a database has multiple schemas because there are no schema creation statements emitted. Insert statements for export also need to prefix table names with schema name. This problem has been fixed. </li><li>DatabaseMetadata now show a foreign keys for other schemas when logging in as SYSDBA. </li><li>ADMIN is still a keyword, but not a reserved one. </li><li>When two separate threads are allocating a new log file at the same time, the potential for a deadlock no longer occurs. </li><li>SHOW DDL did not generate "CREATE SCHEMA" statements. This is needed if the output is to be executed against another database. </li> <li>Foreign keys are now reported in show ddl for non-default schema when logged in as sysdba (administrator). </li><li>Show ddl command now works for a table with an autoincrement column. </li><li>An exception is reported when there are two tables with foreign keys that reference each other, and both tables are being updated by separate transactions a lock timeout error can occur. This has been fixed. </li><li>Wrong result from running join query has been fixed. </li></ul> <h3><a name="fixed_701">Bugs Fixed in 7.01</a></h3><ul><li>Modify output of date and time to include at least 2 digits for day, month, minute, second, hours. </li><li>Remote JDBC driver improved server exception handling. </li><li>A prepared query with a parameterized LIKE operator in the where clause e.g. "SELECT * FROM PERSON WHERE LASTNAME LIKE ?"was mistakenly executed with the parameter given first time the query was executed; thus subsequent executions would receive wrong results. This problem has been fixed. </li><li>A SQL query which uses an auto-increment field for a lookup or join may in certain circumstances yield the wrong result. This problem has been fixed. </li><li>Tables with a column named INTERNALROW, could not be exported using ISQL. This problem has been fixed. </li><li>The data presented in the ServerConsole and the SQL tab in JdsExplorer for a query like: "SELECT * FROM MY_VIEW" could not be edited even if the view was updateable. This problem has been fixed. </li><li>TxException LOCK_TIMEOUT errors fixed for situations where table lock escalation is triggered to max row locks exceeded. </li><li>Problem when value from source cursor had a maxInline setting that was larger than the destination cursor. Cursor now can convert inline into blob if necessary. </li><li>Drop column no longer fails to have any affect if another connection has a prepared statement that references the same table. </li><li>The command SHOW TABLE in ISQL required an explicit schema name. This problem has been fixed. </li><li>Cannot drop primary mirror. Problem is now fixed. </li> <li>ResultSetMetaData now returns the correct column count when an updateable ResultSet is used. </li><li>Column from Primary keys were sometimes reported to be nullable through DatabaseMetadata.getColumns().This problem has been fixed. </li><li>If 2 timestamp values are given as 2 literals the first value is stored for both values. This problem has been fixed. </li><li>The Date and Timestamp literal JDBC escape formats were incorrectly documented. This problem has been fixed. </li></ul> http://cc.embarcadero.com/Item/25372 2008-05-13T22:14:54 2008-05-13T22:14:54 http://cc.embarcadero.com/Item/25372 These files are the companion files for a white paper on using JDataStore for Mobile/Embedded database applications. http://cc.embarcadero.com/Item/18676 2003-06-05T20:50:43 2003-06-05T20:50:43 http://cc.embarcadero.com/Item/18676