Softpedia >Windows >Programming >Other Programming Files >Awake SQL >  Changelog

Awake SQL Changelog

What's new in Awake SQL 2.0

Jun 8, 2013
  • New features:
  • License is now GPL v3.
  • Name is now Awake SQL because there is a unique edition which is the merge of previous CE (Community Edition) & EE (Enterprise Edition)
  • SQL transactions support (Commit & Rollback) including Savepoints.
  • AutoGeneratedKeys support.
  • Simultaneous connections to different databases in the same client-side session.
  • Thread safe accesses to remote databases. (Example: running one query in the main thread and another in a background thread.)
  • Blobs and Clobs support with no size limits.
  • More security rules are available. See User Guide.
  • Datalinks support.
  • Arrays support.
  • RowId support.
  • Session management: default behavior is to attribute the same server JDBC Connection to a logged user during his session. The Connection is thus stored in memory by Awake SQL during the user session, until the user logoffs by closing his Connection on client side.
  • Stateless mode sill exists but is not anymore the default session behavior. A client side boolean allows to chose the session behavior at client side startup. See User Guide.
  • Better security: java.io.tmpdir is not anymore used on
  • server side for files upload/download.
  • Uses new 1.3 version of Apache Commons Fileupload.
  • Uses new 4.2.5 version of Apache HttpClient.
  • Uses new 7.0.40 version of Apache Tomcat JDBC Pool.
  • Uses new 2.2.4 version of Gson.
  • Fixed bugs:
  • There was a bug in AwakeSqlConfigurator.allowStatementAfterAnalysis() call.
  • The parameters List parameterValues would be empty for String
  • parameters. This has been fixed.

New in Awake SQL 1.3 (Oct 26, 2012)

  • New features:
  • Product name is now Awake SQL Community Edition. Awake SQL has been split between Awake SQL Community Edition & Awake SQL Enterprise Edition.
  • The two products share the same core code, but some advanced features have been migrated to Awake SQL Enterprise Edition.
  • Communication protocol between client and server has been rewritten using fast JSON.simple for most data exchange (instead of Google GSon).
  • Fixed bugs:
  • Client class FileNameFromBlobBuilder would refer the Server side StatementAnalyser.
  • This would break the rules in User Tutorial about how to separate client & servers classes for obfsucation.This has been fixed.
  • Authentication Token was not always unique due to a bug. This has been fixed.
  • Upgrading from previous version 1.2.2:
  • Because communication protocol has been changed: client side needs to be re-deployed.
  • (Previous client side 1.2.2 will not work with new server side 1.3).
  • Binary compatible both on client and server side: you don't need to recompile your source code.

New in Awake SQL 1.2.2 (Sep 18, 2012)

  • New features:
  • MS Access 2010 is now supported.
  • Fixed bugs:
  • A ResultSet was not closed on the server side when calling Connection.getMetaData(). This has been fixed.
  • PreparedStatement.setBytes() would set a wrong value with additional bytes. This has been fixed.

New in Awake SQL 1.2 (Aug 1, 2012)

  • New features:
  • Android is now supported on the client side with a dedicated packaging.
  • Terradata database 13+ is now supported.
  • Auto-generated keys retrieval is now supported.
  • Fixed bugs:
  • Client class FileNameFromBlobBuilder would contain a reference
  • to server class StatementAnalyser. This has been fixed. This was necessary
  • for users who want to shrink client side by removing unnecessary server classes.
  • StatementAnalyser would not support the syntax:
  • "insert into table (col1, col2, ,..., coln) values ( ?, ?, ..., ? )"
  • This has been fixed.

New in Awake SQL 1.1.4 (Aug 1, 2012)

  • New features:
  • ResultSet creation and getXxx() methods have been optimized and are now faster.
  • Fixed bugs:
  • The Connection of running SQL command would be automatically closed after 60 seconds. This has been fixed.

New in Awake SQL 1.1.3 (Aug 1, 2012)

  • New features:
  • If AwakeCommonsConfigurator.forceSecureHttp returns true, the client side
  • automatically and silently updates the "http" scheme to "https" prior to
  • authentication (username & password will be sent using https).
  • It is now possible to use self-signed SSL Certificates on the server side.
  • See org.awakefw.commons.api.client.HttpProtocolParameters Javadoc.

New in Awake SQL 1.1.2 (Aug 1, 2012)

  • Fixed bugs:
  • Awake SQL Version was not displayed correctly at Servlet container startup. This has been fixed.
  • Misc Javadoc bugs.

New in Awake SQL 1.1.1 (Aug 1, 2012)

  • Awake SQL v1.1 Maven implementation was invalid due to an upload error and
  • could not work correctly. Because Maven versions can not be undone or corrected on Maven Central, it's cleaner to generate a new version for all users,
  • Maven or not.

New in Awake SQL 1.1 (Aug 1, 2012)

  • New features:
  • New methods added to AwakeSqlConfigurator to enhance server server security: allowExecute, allowExecuteUpdate, allowStatementClass.
  • Some AwakeSqlConfigurator methods have been renamed:
  • allowExecuteAfterAnalysis ==> allowStatementAfterAnalysis & runIfExecuteDisallowed ==> runIfStatementRefused &
  • allowGetResultSetMetaData ==> allowResultSetGetMetaData.

New in Awake SQL 1.0.13 (Aug 1, 2012)

  • New features:
  • A complete diagnosis with full stack trace is available both on client and server side when an AwakeCommonsConfigurator or AwakeSqlConfigurator throws an Exception.
  • Java version is tested in AwakeConnection constructors.
  • The HTML encoding supports non-ASCII characters (allows support for all languages).

New in Awake SQL 1.0.12 (Aug 1, 2012)

  • New features:
  • Cleaner messages if user AwakeCommonsConfigurator implementation throws an Exception.
  • Cleaner and mored detailed messages on client side if JDBC Connection
  • can not be created on the server side.
  • The method Connection getConnection(String username, String password)
  • has been removed from AwakeCommonsConfigurator. (Could never be used,
  • this was a design mistake).
  • Misc Javadoc cleaning.
  • Fixed bugs:
  • Some InputStream were not correctly closed when uploading a blob/clob. This has been fixed.
  • The progress value (for Progress Monitors) was never set to 100 when downloading a Blob/Clob. This has been fixed.

New in Awake SQL 1.0.11 (Aug 1, 2012)

  • New features:
  • Remove AwakeSQLException (use instead SQLException as wrapper).
  • Remove AwakeSecurityException and use instead java.lang.SecurityException.
  • Rename AwakeRemoteException to RemoteException.
  • PreparedStatement.executeQuery() is almost twice as fast
  • use of simple json 1.1 library).
  • Cleaner SQLException messages if server side can't build the Awake
  • Connection pool.
  • PreparedStatement.setAsciiStream and ResultSet.getAsciiStream are now
  • supported to upload/download Clobs.
  • The HttpProtocolParameters.setHtmlEncodingOn method allows to define
  • if the text contained in a Clob a must be html encoded before Clob upload
  • or download.
  • The AwakeCommonsConfigurator.computeAuthToken method is now documented in
  • Tutorial.
  • The HSQLDB (HyperSQL Database) Java database is now supported.

New in Awake SQL 1.0.10 (Aug 1, 2012)

  • Fixed bugs:
  • awake-sql-1.0.10.jar contained many examples (due to a generation error).
  • Misc Javadoc errors.