You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ar...@apache.org on 2006/07/12 02:03:18 UTC
svn commit: r421042 - /db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt
Author: arminw
Date: Tue Jul 11 17:03:18 2006
New Revision: 421042
URL: http://svn.apache.org/viewvc?rev=421042&view=rev
Log:
update notes till OJB-118
Modified:
db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt
Modified: db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt
URL: http://svn.apache.org/viewvc/db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt?rev=421042&r1=421041&r2=421042&view=diff
==============================================================================
--- db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt (original)
+++ db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt Tue Jul 11 17:03:18 2006
@@ -18,37 +18,32 @@
Release 1.0.5
---------------------------------------------------------------------
NEW FEATURES:
-- [OJB-105] - Pluggable "null" definition for persistent fields.
+* [OJB-105] - Pluggable "null" definition for persistent fields.
Restriction: no consistency checking between PK-field and fields used for referring the PK.
-- Better support for attributes containing expressions ie. sum(0.9 * price * stock).
+* [OJB-73] - generate onDelete="cascade" for foreign-key element if auto-delete is set to true
+ for collection descriptor
+* [OJB-107] - Support for Clob/Blob field types in persistence capable objects
+* Better support for attributes containing expressions ie. sum(0.9 * price * stock).
Restriction: All attributes contained in the expressions have to belong to the same table !
-- Add new CGLib based PersistentField implementation. It requires JavaBeans compliant
+* Add new CGLib based PersistentField implementation. It requires JavaBeans compliant
getter/setter. It's three times faster than the direct field access via reflection.
-- new support for quoting table and column names
+* new support for quoting table and column names
the ojb quoting character is '. this character is replaced with the platform
specific character when generating the sql.
'myTable' will be converted to "myTable", [myTable] etc. depending on Platform#getQuotedName
-- Relationships based on non primarykey fields. These fields are defined in the new
+* Relationships based on non primarykey fields. These fields are defined in the new
attribute "target-field-ref" of inverse-foreignkey and foreignkey in collection- and
referenceDescriptor. If the target-field-ref is missing the primary key of the referenced
class is used.
<class-descriptor
- class="org.apache.ojb.broker.NoPkReferenceTest$Article_2"
- table="Artikel_2" >
+ class="org.apache.ojb.broker.NoPkReferenceTest$Article_2" table="Article_2" >
<field-descriptor
- name="articleId"
- column="Artikel_Nr"
- jdbc-type="INTEGER"
- primarykey="true"
- autoincrement="true"
- />
+ name="articleId" column="articleId" jdbc-type="INTEGER"
+ primarykey="true" autoincrement="true"/>
...
<field-descriptor
- name="productGroupName"
- column="KatName"
- jdbc-type="VARCHAR"
- />
+ name="productGroupName" column="KatName" jdbc-type="VARCHAR"/>
...
<reference-descriptor
name="productGroup"
@@ -59,25 +54,12 @@
</class-descriptor>
<class-descriptor
- class="org.apache.ojb.broker.NoPkReferenceTest$ProductGroup_2"
- table="Kategorien_2" >
+ class="org.apache.ojb.broker.NoPkReferenceTest$ProductGroup_2" table="Categories_2" >
<field-descriptor
- name="groupId"
- column="Kategorie_Nr"
- jdbc-type="INTEGER"
- primarykey="true"
- autoincrement="true"
- />
+ name="groupId" column="productGroupId" jdbc-type="INTEGER"
+ primarykey="true" autoincrement="true" />
<field-descriptor
- name="groupName"
- column="Kategorie_Name"
- jdbc-type="VARCHAR"
- />
- <field-descriptor
- name="description"
- column="Beschreibung"
- jdbc-type="VARCHAR"
- />
+ name="groupName" column="Category_Name" jdbc-type="VARCHAR"/>
<collection-descriptor
name="allArticlesInGroup"
element-class-ref="org.apache.ojb.broker.NoPkReferenceTest$Article_2"
@@ -89,27 +71,53 @@
</collection-descriptor>
</class-descriptor>
+IMPROVEMENT:
+* [OJB-88] - Documentation: Adapt LOB's howto, add docs for CLOB
+* [OJB-100] - Allow the specification of names for database foreignkeys and indices
+* [OJB-101] - Add support CLOB support in PlatformOracle9iImpl for XAPool prepared statements.
+* [OJB-109] - Location of repository.xml
+* [OJB-111] - Add PersistenceBroker leak detection (details see documentation and OJB.properties file)
+
NOTES:
-- OJB.properties, repository.dtd files changed, replace it.
-- Documentation update and improvement: section about using RowReader and using a
+* OJB.properties, repository.dtd files changed, replace it.
+* Documentation update and improvement: section about using RowReader and using a
specific RowReader on class level, section "performance" reworked, LOB content
howto reworked, FAQ improved.
CHANGES:
-- PersistenceBroker interface: new method #serviceLobHelper() added
-- RowReader interface: new method #readValuesFrom(ResultSetAndStatement rs, Map row, FieldDescriptor[] fields)
+* PersistenceBroker interface: new method #serviceLobHelper() added
+* RowReader interface: new method #readValuesFrom(ResultSetAndStatement rs, Map row, FieldDescriptor[] fields)
added (to improve LOB field support)
-- ODMG-api implementation, internal used locking interface changed to improve performance.
+* JdbcAccess implementation constructor changed.
+* ODMG-api implementation, internal used locking interface changed to improve performance.
+* Upgraded Torque to version 3.2
BUG FIXES:
Please refer to our Bug tracking site (https://issues.apache.org/jira/browse/OJB)
to see details for a bug with id OJB-xxx.
-- Fixed: Batch handling doesn't work properly with optimistic locking. Now OJB temporarily disable
+* Fixed: Batch handling doesn't work properly with optimistic locking. Now OJB temporarily disable
batch-mode for all objects using optimistic locking on update/delete operations.
-- Fixed: Batch handling doesn't work properly on insert when database identity columns are used.
+* Fixed: Batch handling doesn't work properly on insert when database identity columns are used.
Now OJB execute the batch statement after insert of objects using identity columns.
-- Fixed: Batch handling doesn't work proper when adding new class-descriptor at runtime and when
+* Fixed: Batch handling doesn't work proper when adding new class-descriptor at runtime and when
using different metadata profiles.
+* [OJB-85] - ODMG-api in managed environment: Transaction demarcation problems when
+ using a ConnectionFactory different from deprecated ConnectionFactoryManagedImpl
+* [OJB-86] - OJB expects in method Implementation#newOQLQuery() an illegal return type
+* [OJB-89] - ODMG: The LockManagerFactory doesn't configure LockManager implementations
+ which using OJB's Configurable interface
+* [OJB-90] - Collection proxies do not follow equals/hashCode contract
+* [OJB-91] - Query performance slowdown (about 20%) between 1.0.3 and 1.0.4
+* [OJB-93] - Super class record not being deleted.
+* [OJB-94] - NPE when execute query (join via 1:n reference) on objects using "table-per-subclass"-inheritance
+* [OJB-97] - ConnectionFactoryDBCPImpl: Rollback call after commit call when set useAutoCommit="2"
+* [OJB-98] - OJB statup failure after update 1.0.3 -> 1.0.4
+* [OJB-103] - TransactionExt.flush() call doesn't clear 1:1, 1:n link history
+* [OJB-113] - Fix support for JAVA_OBJECT jdbc type
+* [OJB-114] - Concurrency issue with between RsIterator.finalize() and PersistenceBrokerAbstractImpl.
+* [OJB-117] - OJB can't read metadata provided by separate jar file (in classpath)
+* [OJB-118] - odmg-api, if two new object (associated via reference) are registered and deleted
+ within the same tx, odmg perform illegal insert of one object
KNOWN ISSUES:
* Auto-Detection for insert/update objects checks to avoid DB queries the PK fields of the object.
@@ -126,6 +134,7 @@
in production environments. The future of the OTM layer will be subject for discussion on the
OJB developers list, if you are using it - please subscribe to ojb-dev and make your voice heard.
* Oracle9i platform: when using statement batching, there is a 2k limit on BLOB + 4k limit on CLOB.
+
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org