Signsoft intelliBO Changelog
Version 4.1.3
- core
- » [08.04.2008] bugfix:
- Avoid unnecessary statements if inverse relations are used.
- » [10.03.2008] bugfix:
- Sort insert, update and delete statements to avoid unnecessary flushes in mixed batchable and not batchable workloads.
- » [05.03.2008] bugfix:
- Incompletely registered object models are recognized as error.
- » [27.02.2008] bugfix:
- Better support for JDOQL Queries with down casts.
- » [25.02.2008] bugfix:
- Better support for JDOQL Queries with nested (allow null) relations and THIN inheritance hierarchies.
- » [20.02.2008] bugfix:
- Better support for JDOQL Queries with navigations and hidden datastore identity object models.
- » [19.02.2008] bugfix:
- Better support of Timestamp values if used in exchange operations.
- » [18.02.2008] bugfix:
- Better support of JDO Queries which use parameters as collections, and the usage of contains().
- » [11.02.2008] bugfix:
- Nested relations defined via fetch groups are now selected correctly.
- » [07.02.2008] bugfix:
- Removed wrong Left Outer Joins in relations into thin inheritance hierarchies.
- » [01.02.2008] bugfix:
- Removed wrong Left Outer Join hierarchy in relations into thin inheritance hierarchies.
- » [29.01.2008] bugfix:
- Avoided NullPointerException with an invalid navigation in the order-by-part of a query.
- » [18.01.2008] bugfix:
- Correctly set the test statement for database connection health checks.
- » [08.01.2008] feature:
- Support for JDO2 javax.jdo.option.DetachAllOnCommit flag.
- » [08.01.2008] change:
- Version string added in file name for Log4J library.
- » [08.01.2008] bugfix:
- Fixed null value management for JDO 2.0 compliance.
- » [27.11.2007] bugfix:
- Verifier reported wrongly, that exchange operation is not implemented.
- » [23.11.2007] feature:
- JDO2 specific methods, wich are shortcuts for already existing funtionality were implemented.
- » [23.11.2007] bugfix:
- Problems on loading of hidden fields with persistent-new objects were solved.
- » [24.10.2007] bugfix:
- Problems with reverse relations and multi-table-keys were solved.
- » [3.12.2007] bugfix:
- Problems with complex JDOQL Filters were solved. Wrong Left Outer Joins wer generated.
- samples
- » [26.02.2008] feature:
- A sample for using down-casts in JDOQL queries was added.
- » [18.02.2008] feature:
- One more sample for JDO2 fetch-groups was added.
- tools
- » [18.02.2008] feature:
- The SQLRunner task now supports the settings 'encoding' and 'expandProperties' in accordance with Ant's SQL task.
Version 4.1.2
- core
- » [17.10.2007] bugfix:
- Problems with Enum mappings and non-int keys were solved.
- » [16.10.2007] bugfix:
- Writing and reading LOB fields on an Oracle datasource in BEA WebLogic caused a java.lang.AbstractMethodError.
- » [16.10.2007] bugfix:
- Problems with base navigations in user-defined JDOQL functions were solved.
- » [13.10.2007] feature:
- The order of statements during commit() or flush() (insert, update, delete) now may be configured be the property datastore-write-order.
- » [10.10.2007] change:
- Access to a field which was not loaded applies the current fetchplan to the master object only if the field is part of the fetchplan.
- » [28.09.2007] change:
- The iboaux.jar file is now deliverd in partly exploded form.
- » [28.09.2007] bugfix:
- The parameter "test-statement" in the file ibo-config.xml was not evaluated.
- » [28.09.2007] bugfix:
- The log4j.properties configuration file is no longer included in ibo.jar.
- » [20.09.2007] feature:
- Enum mappings now also allow to use Strings as the enum database code.
- » [18.09.2007] bugfix:
- The enhancer generated wrong byte code for additional key fields in derived classes.
- » [14.09.2007] bugfix:
- Optional relation and application identity. It was tried to write a null value via reflection to a primitive field.
- » [13.09.2007] bugfix:
- A write access on a not yet loaded refernce field (1:1 mapping) lead to a wrong dirty detection. Foreign keys were updated correctly.
- » [13.09.2007] bugfix:
- JDOQL filters with nested braces were not correctly evaluated. Errors occured because of unsupported AST elements while creating IQL.
- » [03.09.2007] change:
- The web sample was switched to the Struts2 framework.
- » [28.08.2007] regression:
- The usage of arrays in 1:n and m:n relations caused an exception while sorting results of queries.
- » [22.08.2007] regression:
- The usage of arrays in 1:n and m:n relations caused a NullPointerException while resolving fetchplans.
- » [20.07.2007] bugfix:
- The SchemaGen-Anttask ignored username and password when creating update scripts.
- » [20.07.2007] feature:
- The support of Derby, MySQL and McKoi was improved.
- » [16.07.2007] feature:
- The options StatementBatchSize and StatementBatchType can now also be set via a properties file.
- samples
- » [20.09.2007] feature:
- A second sample was added to examplify the use of enum mapping.
- » [05.09.2007] feature:
- The sample can now be all together coonverted to Eclipse projects by help of an Ant script.
- » [05.09.2007] feature:
- The architecture samples are now sipped with a h2.xml Ant file, to start and stop the H2 database in TCP server mode.
- » [05.09.2007] change:
- The structure of the samples was significantly simplified. Now also Ant beginners will identify and use the intelliBO tools without difficulty.
- tools
- » [05.09.2007] change:
- The db-config.xml file is no longer supported. The information can now be given via the ibo:dbconfig-element in the Ant build.xml file.
- » [05.09.2007] change:
- The naming of the parameters of the ibo:dbconfig-element have slightly changed. 'databasesupportclassname' now refers to the class name of the db-support class, 'databasesupportrules' refers to the type mapping file of the schema generator. The format of this setting is now explicitly '/dbsupport_xyz.xml'.
- » [04.09.2007] change:
- The Ant tasks of the intelliBO tool no longer need the attributes 'stacktrace' and 'verbose'. They are replace by the overall settings of the Ant skript.
Version 4.1.1
- core
- » [22.06.2007] bugfix:
- Accessing unloaded reference fields with an active empty fetch plan did not deliver any detail objects even if they existed.
- » [22.06.2007] bugfix:
- The shared cache did not reconstruct collections correctly after executing a query with a user defined fetch plan.
- » [20.06.2007] bugfix:
- A warning will be emitted if statement pre-odering is activated without a configuration file being present.
- » [20.06.2007] change:
- The default value for shrink-frequency is -1 (=pool shrinking deactivated).
- » [19.06.2007] feature:
- Mapping descriptions may be validated against XML schema and all official JDO document types.
- » [12.06.2007] change:
- Objects which were created in jdoPreStore will be persisted.
- » [12.06.2007] bugfix:
- A query with '== null' for a reversely-mapped 1:1 relation now generates a correct SQL statement.
- samples
- » [27.06.2007] feature:
- Samples for the usage of fetch plans and detach/attach were added.
- » [21.06.2007] feature:
- An architecture sample for using Signsoft intelliBO with Spring 2 was added.
- » [21.06.2007] change:
- The Spring 1 sample was rewritten to better exemplify the usage of attach/detach with Spring.
- tools
- » [15.06.2007] change:
- The update URL for the eclipse plug-in has changed.
- » [14.06.2007] bugfix:
- The ibolic tool ignored command line parameters. (Professional)
Version 4.1.0
- core
- » [15.05.2007] change:
- The JDO2 classes and interfaces are shipped in a separate jdo2.jar in the Professional Edition. This jar fie is necessary for executing the tools and the runtime environment.
- » [15.05.2007] change:
- intelliBO is now shipped with the JDO 2.0 interfaces. Functionality which is not yet supported throws an IBOJDOException with error code 1041.
- » [02.05.2007] change:
- The PersistenceManagerFactory can be configured according JDO 2.0 specification.
- » [02.05.2007] feature:
- Architecture samples to demonstrate the use of Signsoft intelliBO in Spring or EJB3 environment has been added.
- » [02.05.2007] feature:
- Attaching and detachaching of persistent objects is supported according JDO 2.0 specification. The transport container functionality from older versions is no longer supported.
- » [02.05.2007] feature:
- Fetch-groups and fetch-plans are supported according JDO 2.0 specification.
- » [02.05.2007] change:
- Support of JDBC/Java datatype combination was enhanced.
- » [02.05.2007] feature:
- The included samples can be run out-of-the-box on a H2 database.
- » [30.04.2007] change:
- It is possible to specify the scroll type of the created statement for a DirectSQLQuery.
- » [05.04.2007] change:
- Foreign key relations for mixed batch mode operations are now correctly sorted.
- » [02.04.2007] change:
- Correctly sorted SQL-order-by-segments are now created even for complex order-by settings in a JDO query.
- » [22.03.2007] change:
- Statement batching with Oracle databases can now be enabled for objects with LOB fields.
- » [21.03.2007] bugfix:
- Corrected generated statements for query with negated implicit references in a query (address != o)is now generated.
- » [21.03.2007] change:
- Classes that are used in JDOQL queries must be fully qualified or imported via declare-imports.
- » [15.03.2007] bugfix:
- In complex query filters redundant joints could occur.
- » [15.03.2007] bugfix:
- Problems with JDOQL filters with contains and 1:1 relations were fixed.
- » [21.02.2007] bugfix:
- Better error messages for the use of incorrect navigations in in memory query.
- » [08.02.2007] change:
- Datastore identities: In the course of memory optimizations, the internal representation of datastore identities was changed.
- » [10.01.2007] change:
- Optional relations between data objects: If an association is optional, i.e. a null reference is allowed, the JDO mapping file must explicitly state an "allow-null" for this relation.
- » [10.01.2007] change:
- PersistenceManager#getObjectById(oid, validate=true): Calling getObjectById() on a PersistenceManager does not cause a refresh of an already fetched object any more.
- » [10.01.2007] change:
- Fetching on demand: To improve JDO 2.0 conformance, an access to a not-yet-loaded field leads to a fetch of the whole default fetch group or the currently active fetch group.
- enhancer
- » [16.05.2007] change:
- The enhancer now generates JDO 2.0 compatible classes. Due to a change in the JDO interfaces already existing enhanced classes may not be reused and must be enhanced again. This does not require further changes to classes or mappings.
- schemagen
- » [02.05.2007] bugfix:
- The schemagen generates correct SQL-create-table-scripts for all supported databases.
|