Michael -- When you add the criteria "mycollection.someOtherField=value2", you are essentially telling ojb that you want any instance of "O" that has an entry in the "mycollection" collection where the attribute "someOtherField" is equal to "value2". Specifying this criteria will have no impact on the contents of "mycollection" when you access it from an instance of "O" that is returned by the crtieria. Unless you use a query-customizer, the collection "mycollection" will contain all entries from the corresponding table that are related to the "O" instance.
Ron Gallagher Atlanta, GA [EMAIL PROTECTED] > > From: Michael Newman <[EMAIL PROTECTED]> > Date: 2003/07/24 Thu AM 05:12:34 EDT > To: [EMAIL PROTECTED] > Subject: collection filtering from inverse relations > > I have the following problem with OJB broker queries: > > In an object O we refer to a collection C named "mycollection" with "inverse- > foreignkey". When we make a build criteria, we add someField=value1 and > mycollection.someOtherField=value2. "someField" belongs to O. > The result is correct based on criterias for fields from O but it does not > filter the collection "mycollection" based on the field "someOtherField". It > retrives all the references to the parent object. > > Does anyone know what might be the problem or this is the correct behavior? > > Thanks, > -- > Michael Newman > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
