Strange queries in Many to One relationship

[brown1d]

Hi,

I have a problem with the queries being generated against my database (PostgreSQL) using JBoss-3.0.0. The application takes advantage of the new CMP code.

From the logs it can be seen when I create a new customer object the system gets the appropriate status object and then for some reason selects all the Customers with that status.

Anyone got any idea why this is happening and how I can avoid it?

Regards,
Dave.

CustomerEJB (Many) -> CustomerStatusEJB (One)

2002-06-23 10:06:41,115 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.CustomerStatusEJB] Executing SQL: SELECT status FROM customerstatusejb WHERE (id=?)
2002-06-23 10:06:41,119 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.CustomerStatusEJB] Executing SQL: SELECT id FROM customerejb WHERE (status=?)

<!-- Customer - CustomerStatus -->
<ejb-relation>
<ejb-relation-name>CustomerEJB-CustomerStatusEJB</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>CustomerEJB</ejb-relationship-role-name>
Many
<relationship-role-source>
<ejb-name>CustomerEJB</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>status</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>CustomerStatusEJB</ejb-relationship-role-name>
One
<relationship-role-source>
<ejb-name>CustomerStatusEJB</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>

[dsundstrom]

What exactally is wrong with the query?

[brown1d]

As part of the creation of the CustomerEJB it does the following:

CustomerStatus status = CustomerStatusHome.findByPrimaryKey(1);

This seems to be where the problem occurs. It looks up that CustomerStatus entity, and then all the Customers with that status.

It is the second part I wish to stop.

Dave.

[dsundstrom]

Relationships user referencial integerity, so the container need to verify that there are no entities assigned to this relationship in the database. There is no way to disable it, as without the check you can end up with an inconsistent database state.