auto-delete setting in 1:n relationships

Hello, when setting auto-delete="link" in 1:n relationships the documentation states that this behaves like "none". What are the reason for not unlinking the referenced objects? Take the Article ProductGroup example. Why does auto-delete = "link" for ProductGroup does not set productGrou

Oracle Null value for prepared select statement

Hi, I am using an OQLQuery with a parameter that is nullable. e.g. "Select all from class1 where field2 = $1 and field3 = ?2" The underlying JDBCImpl uses a PreparedStatement and sets this parameter to null (with setNull(..). e.g "select column1, column2, column3 from table1 where

Oracle Null value for prepared select statement

Hi, I am using an OQLQuery with a parameter that is nullable. e.g. "Select all from class1 where field2 = $1 and field3 = ?2" The underlying JDBCImpl uses a PreparedStatement and sets this parameter to null (with setNull(..). e.g "select column1, column2, column3 from table1 where

need better understanding of adding and removing to 1:n collections

this really necessary and why? Thanks, Vincenz Braun - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Problem with anonymous keys in 1:n back-mapping (again)

the main difference is that you use anonymous primary-keys but this > should not cause troubles. imo you'll have to materialize > transition to > get the fields filled. > > see RowReaderDefaultImpl#buildWithReflection (i set a breakpoint in > AnonymousPersistentField#

RE: Problem with anonymous keys in 1:n back-mapping (again)

n="id" > jdbc-type="INTEGER" > primarykey="true" >autoincrement="true" >/> > name="idPerson" > column="idPerson" > jdbc-type="INTEGER" &

Problem with anonymous keys in 1:n back-mapping (again)

Hello, I have the same problem described earlier in this list by Gerhard Grosse. What is the status of this issue? Is someone working on this or has at least committed a bug report? I queried scarab and did not find a matching issue, yet. Any help greatly appreciated. Vincenz original post from

Problem with anonymous keys in 1:n back-mapping (again)

Hello, I have the same problem described earlier in this list by Gerhard Grosse. What is the status of this issue? Is someone working on this or has at least committed a bug report? I queried scarab and did not find a matching issue, yet. Any help greatly appreciated. Vincenz original post from

temporary fix for null foreign key references

Hello everybody, does anybody has a workaraound or temporary patch for the null foreign key reference bug in OJB? This bug was reported twice in scarab. It occurs when inserting or updating objects that have a null foreign key reference. When using primitives (integer etc. ) as a primary key for

Multiple unique keys per table

Does anyone have experience with multiple unique keys per table in ojb and would like to share? Consider the following scenario. I have Table A with two unique keys: 1. one one-column primary key (autoincremented) 2. one 3 column unique key (2 references) Objects of ClassA are made persistent t

Multiple unique keys per table

Does anyone have experience with multiple unique keys per table in ojb and would like to share? Consider the following scenario. I have Table A with two unique keys: 1. one one-column primary key (autoincremented) 2. one 3 column unique key (2 references) Objects of ClassA are made persistent t

misleading documentation regarding auto settings in refence and collection descriptors

Hello, the advanced o/r tutorial says: These default settings are mandatory for proper operation of the ODMG and JDO implementation. In the following code sample, a reference-descriptor and a collection-descriptor are configured to use cascading retrieve (auto-retrieve="true" ), insert and

ejb deployment: reasons for binding the factories?

Hello, I wonder why the PBFactory or ODMG Implementation is bound to a Context. For OMDG this would make sense to me if there were a TransformFactory like interface for getting the implementation class (so one can transparently use another implementation). What are the reasons why not simply use t

RE: Non-Decomposed collections, without implicit locking

I want to know if I have the same problem: I have a User and a Role class. User has a roles:Collection property. The repository defines the collection-descriptor with all auto- values set to true and a indirection-table UserRoles with userId and roleId has a compound primary key. I am using the O

Newbie questions (oracle and ojb setup) (posted because archive unbrowsable)

Hi, my first steps with ojb. Some questions have arised. I post these because it is currently not possible to browse the archive under http://archives.apache.org/eyebrowse/[EMAIL PROTECTED] org. All message bodies are empty :-( I want to use ojb with a sample oracle schema. I wonder where to sp