Armin, I didn't use "ojbConcreteClass" setting in my persistent objects.
I'm going to try to do it now but through Row Reader implementation instead. Thank you, Max. -----Original Message----- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Friday, July 02, 2004 12:18 PM To: OJB Users List Subject: Re: Missing columns in result set Hi Max, do you use "ojbConcreteClass" setting in your persistent objects? http://db.apache.org/ojb/docu/guides/advanced-technique.html#Mapping+All+Classes+on+the+Same+Table We need more info, please post the metadata mapping for the classes. regards, Armin Vesely, Maxim [IT] wrote: > Hello, > > I have two concrete classes mapped to the same table/view in database. There's a > subtle difference in a list of properties these two implement. I remember reading in > documentation that OJB framework optimizes it by retrieving all of the columns > listed in both <class-descriptor> items from database in this case. > > When I run a query I see only columns from one class in a SELECT statement but OJB > fails with the message that it's unable to find a column that is declared as a > <field-descriptor> in another class. Could you, please, point me out in the right > direction here. I'm pretty sure that it works as I've done in the past. > > Thank you, > Max. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
