pointrelnotes.txt

vxworks下的一个嵌入式实时数据库,可以分析源码.

PLATFORMS...: w32, l2x, hia64, jdbc
RELEASE DATE: June 30, 2005

BUG FIXES
---------

SHORT DESCRIPTION: Bulk free implemented to ssffmem.
TPR #: 870067
LONG DESCRIPTION: This fixes memory leaks when using accelerator/hsb netcopy with
    [MME]ReleaseMemoryAtShutdown=No

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.230
BUGS FIXED..: 1 (#870065)
ENHANCEMENTS: 
PLATFORMS...: hia64
RELEASE DATE: June 17, 2005

BUG FIXES
---------

SHORT DESCRIPTION: Changing system time causes HSB connection failure.
TPR #: 870065
LONG DESCRIPTION: When system was changed HsB ping timeout did not detect
    this correctly. This caused erroneous timeout and connection break.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.229
BUGS FIXED..: 2 (#452775, 452816)
ENHANCEMENTS: 1 (#12031)
PLATFORMS...: l2x, w32, jdbc
RELEASE DATE: June 15, 2005

BUG FIXES
---------

SHORT DESCRIPTION: SOLID shutdowns when stored procedure is called.
TPR #: 452775
LONG DESCRIPTION: If the defined length of the return parameter for 
    character data is shorter than the actual length of the data available 
    for return, the data was not correctly truncated.

SHORT DESCRIPTION: Users with SYS_SYNC_ADMIN_ROLE do not have access to 
    SOLID SmartFlow stored procedures.
TPR #: 452816
LONG DESCRIPTION: Now the necessary privileges are granted to 
    SYS_SYNC_ADMIN_ROLE.


PRODUCT ENHANCEMENTS
--------------------

SHORT DESCRIPTION: Enhancement request for adding the APPINFO information 
    into the solmsg.out.
TPR #: 12031
LONG DESCRIPTION: In addition to messages 30001 and 30009, a APPINFO is
    added to messages 30002, 30003, 30004, 30007 and 30008.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.219
BUGS FIXED..: 1 (#11916)
ENHANCEMENTS: 
PLATFORMS...: l2x, w32, jdbc
RELEASE DATE: April 28, 2005

BUG FIXES
---------

SHORT DESCRIPTION: If HSB primary db crashes, and a log file gets corrupted, 
    the db asserts when restarted.
TPR #: 11916
LONG DESCRIPTION: Now the behaviour has been fixed. If HSB server detects a 
    logical failure during recovery it does not assert but truncates the log 
    file and stops recovery.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.218
BUGS FIXED..: 4 (#11900, 11951, 300038, 452485)
ENHANCEMENTS: 1 (#300022)
PLATFORMS...: w32, l2x, s9x, s8x, jdbc
RELEASE DATE: April 8, 2005


BUG FIXES
---------

SHORT DESCRIPTION: Inserting into a VIEW causes 100% CPU usage
TPR #: 11900
LONG DESCRIPTION: Solid caused 100% CPU usage when trying to insert a row 
    into a view, which contains columns by the same name from multiple 
    tables.

SHORT DESCRIPTION: Descending index on the searched column causes the seach 
    condition not to work.
TPR #: 11951
LONG DESCRIPTION: A bug in estimator has been fixed. Now descending index is 
    handled properly.

SHORT DESCRIPTION: Going backwards in resultset slow with JDBC.
TPR #: 300038
LONG DESCRIPTION: FIX: Optimized the internal data structures. 
    The old structures were extremely slow when scrolling the buffer backwards.

SHORT DESCRIPTION: How to delete failed stuck sync message.
TPR #: 452485
LONG DESCRIPTION: Sync_delete_messages procedure now deletes all orphan 
    messages (e.g. master_id = 0).


PRODUCT ENHANCEMENTS
--------------------

SHORT DESCRIPTION: Enhancement request for supporting scroll sensitive result
     sets in JDBC 2.0 driver.
TPR #: 300022
LONG DESCRIPTION:  Solid JDBC 2.0 driver now supports scroll sensitive result
     sets for both M- and D-tables and their combinations with certain
     limitations. First, in order to be sensitive to committed changes in the
     database, the transaction isolation for the scroll sensitive cursor must
     be set as Connection.TRANSACTION_READ_COMMITTED. Second, in result sets
     that consist of more than one table (i.e. tables are joined) the joining
     of the tables must not be (externally) sorted by the SQL interpreter. If
     the result set is sorted by the interpreter, there is no quarantee that
     the most recent rows will be shown by the scroll sencitive result set
     cursor. The user of the scroll sensitive cursor must define the database
     query in such a manner, that the produced result set does not need
     sorting made by the SQL interpreter. The best bet to make sure that the
     result set is not sorted, is to use primary key fields, or other
     internal indexing fields of the table for joining tables. For example,
     if the SQL interpreter uses merge joining in joining the tables of the
     query, it is highly unlikely that the scroll sensitive cursor will
     always see the most recent values of the tables. Hint: use SQL's
     'explain plan' for designing the queries and make sure no merge joining
     or result set sorting is needed if scroll sensitivity is desired.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.215
BUGS FIXED..: 1 (#452674)
ENHANCEMENTS: 
PLATFORMS...: jdbc
RELEASE DATE: February 22, 2005

BUG FIXES
---------

SHORT DESCRIPTION: Problem when using executeBatch for updates.
TPR #: 452674
LONG DESCRIPTION: SolidPreparedStatement::addBatch method called setNull 
    with wrong index causing an Invalid Parameter Number exception to be 
    thrown under certain circumstances.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.214
BUGS FIXED..: 2 (#11886, 11921)
ENHANCEMENTS: 
PLATFORMS...: w32, l2x, jdbc
RELEASE DATE: February 22, 2005

BUG FIXES
---------

SHORT DESCRIPTION: SELECT COUNT(*) returns incorrect values if where clause 
    contains 'is null' and there is a descending index defined on the searched 
    column.
TPR #: 11886
LONG DESCRIPTION: Fix to NULL and NOT NULL constraints on descending indexes. 
    They did not work correctly and returned wrong rows.

SHORT DESCRIPTION: Syntax error in ALTER TABLE ... SET TABLENAME ... causes 
    DB to crash.
TPR #: 11921
LONG DESCRIPTION: Now a correct error message is returned.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.211
BUGS FIXED..: 5 (#11760, 11833, 452487, 452527, 452556)
ENHANCEMENTS: 
PLATFORMS...: w32, l2x, h1x, s9x, s8x, jdbc
RELEASE DATE: January 31, 2005

BUG FIXES
---------

SHORT DESCRIPTION: SQL query containing 'like null' crashes the server.
TPR #: 11760
LONG DESCRIPTION: Now this is handled correctly.

SHORT DESCRIPTION: Now() does not work correctly when inserting rows
    with timestamps as part of the primary key.
TPR #: 11833
LONG DESCRIPTION: A problem in SQL interpreter is fixed.

SHORT DESCRIPTION: Failure of TIMESTAMP in WHERE clause with UNION.
TPR #: 452487
LONG DESCRIPTION:  A problem in SQL parser was fixed.

SHORT DESCRIPTION: Issue with Solid JDBC Driver and TIMESTAMP fields.
TPR #: 452527
LONG DESCRIPTION: Now time zone conversions (setting and getting time/date/timestamp 
    values in a given timezone) using java.util.Calendar is enabled.'

SHORT DESCRIPTION: SOLID asserts with 882@su0vfil.c on a Netcopy.
TPR #: 452556
LONG DESCRIPTION: Secondary doesn't free global file handle pool in case of 
    timeout. Then the next netcopy tries to initialize gloal file handle pool 
    in secondary and causes assertion because handle pool already exists.
    Now this is fixed.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.210
BUGS FIXED..: 3 (11840, 452523, 452562)
ENHANCEMENTS: 
PLATFORMS...: w32, l2x, jdbc
RELEASE DATE: December 21, 2004

BUG FIXES
---------

SHORT DESCRIPTION: Solid ODBC driver cores on multithreaded use in 
    SQLAllocEnv.
TPR #: 11840
LONG DESCRIPTION: Now the environment handle initialization routine 
    is fixed to prevent simultaneous access from several threads.

SHORT DESCRIPTION: HSB status copy shows active after an admin 
    command 'backup' is issued.
TPR #: 452523
LONG DESCRIPTION: Now HSB status is shown correctly during backup.

SHORT DESCRIPTION: SOLID goes down with unhandled exception on 
    issuing a invalid sql statement.
TPR #: 452562
LONG DESCRIPTION: A memory overwrite bug is fixed. When a 
    long constraint was used with index that can hold only very 
    short values (e.g. CHAR(3)) the long constraint value could not 
    fit into key value buffer allocated for the short key.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.207
BUGS FIXED..: 4 (#452460, 452465, 750087, 940029)
ENHANCEMENTS: 1 (#452373)
PLATFORMS...: w32, l2x, jdbc
RELEASE DATE: November 19, 2004

BUG FIXES
---------

SHORT DESCRIPTION: Missing rows in the the replicas.
TPR #: 452460
LONG DESCRIPTION: Flow version visibility bug is now fixed. 
    Flow version level was released before actual row read level so 
    it was possible that Flow subscribe did not see all rows inside 
    Flow version range.

SHORT DESCRIPTION: Extra rows on the replica after a subscription.
TPR #: 452465
LONG DESCRIPTION: Flow version visibility bug is now fixed. 
    Flow version level was released before actual row read level so 
    it was possible that Flow subscribe did not see all rows inside 
    Flow version range.

SHORT DESCRIPTION: Memory growth problem in hsb primary.
TPR #: 750087
LONG DESCRIPTION: The problem has been fixed. There was no real memory 
    growth but pmon performance counters leaked because of incomplete 
    mutexing.

SHORT DESCRIPTION: Environment variable SOLAPPINFO does not show thru JDBC
TPR #: 940029
LONG DESCRIPTION: Added a property "solid_appinfo" for passing SOLAPPINFO 
    string to the server from a JDBC2 RPC client. Also, the hostname 
    resolving in s_Rpc was changed so that instead of getting the numerical 
    IP address of the machine, the hostname sent to the server is the actual 
    given name of the machine.
	
    SOLAPPINFO is passed to the server either as a command line property or 
    as a property value defined in the java application. 
	
    Command line example:
	
        java -Dsolid_appinfo="This is an appinfo string" <java application name>
	
    The other way is to give the "solid_appinfo" property from the application 
    code like this:
	
        Properties props = new Properties()
        props.put("solid_appinfo", "This is an appinfo string")
        Connection c = Driver.getConnection( "<jdbc connection url>", props)
	
    The property value given in the application code precedes the value given 
    from the command line.

PRODUCT ENHANCEMENTS
--------------------

SHORT DESCRIPTION: Enhancement request to be able to stop a on going backup.
TPR #: 452373
LONG DESCRIPTION:  Admin command 'abort backup' has been implemented in 4.1.
    Now it only aborts disk backup, hsb copy or netcopy cannot be aborted.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.202
BUGS FIXED..: 2 (#11715, 50193)
PLATFORMS...: w32, l2x, jdbc
RELEASE DATE: October 28, 2004

SHORT DESCRIPTION: SQL estimator may choose a bad execution plan.
    TPR #: 11715, 50193
LONG DESCRIPTION:  Added a new configuration parameter 
        [SQL]
        EnableLateIndexPlan=Yes/No 
    Default is No. When set to Yes index selection is done at run 
    time in cases where constraint values are not known at estimate 
    phase. As a side effect the output from EXPLAIN PLAN does not 
    always show correct index selection. Only the first time a value 
    is know the index is selected again. Following calls through the 
    same low level table cursor do not change the index selection any 
    more.

PRODUCT.....: BoostEngine 4.1
VERSION.....: 04.10.195
BUGS FIXED..: 8 (#11731, 20181, 20190, 452111, 452225, 452357, 452379, 940020)
PLATFORMS...: w32, l2x, jdbc
RELEASE DATE: September 30, 2004


SHORT DESCRIPTION: SQL estimator may choose a bad execution plan.
TPR #: 11731
LONG DESCRIPTION: Now estimator calculates index size more correctly. 
    The default minimum table size used for estimator samples was lowered 
    from 500 to 100.

SHORT DESCRIPTION: Concurrent SQLConnect calls may cause Solid ODBC client 
    core in Linux-Intel. 
    TPR #: 20181, 20190
LONG DESCRIPTION:  The implementation of threaded asynchronous gethostbyname
    was changed to avoid problems when the resolver resources are freed.
    Important note for W32 users: TPR #20181 affects also server end 
    communication DLL's. Please update server's communication DLL's
    when updating your solid.exe.

SHORT DESCRIPTION: Version 04.10.141 stores history in the master on deletes 
    even when there are no replicas registered to the master.
TPR #: 452111
LONG DESCRIPTION: Now master counts registered replicas and if the count is 
    zero then history is not collected.