hi jacob, By some miracle now I can see both issues ;)
thank you again, sergey -----Original Message----- From: Jakob Braeuchi [mailto:[EMAIL PROTECTED] Sent: Monday, March 22, 2004 3:44 PM To: OJB Users List Subject: Re: OJB report query hi sergey, can you see other ojb issues ie. OJB179 ? can you access OJB242 when you do not use the link i posted ? jakob Manukyan, Sergey wrote: > thank you jacob, > > I have scarab account and am associated with OJB module, > > sergey > > > -----Original Message----- > From: Jakob Braeuchi [mailto:[EMAIL PROTECTED] > Sent: Monday, March 22, 2004 3:29 PM > To: OJB Users List > Subject: Re: OJB report query > > hi sergey, > > do you have a scarab-account ? > > btw. this is what OJB242 is all about: > > OJB can not resolve criteria or columns containing multiple attributes. > > ie: upper(col1 || col2) > > this leads to problems with distinct count-queries, where we need > concatenation > to construct one distinct value based on the pks: > > SELECT count(distinct (key1 || key2 || key3)) > > > jakob > > Manukyan, Sergey wrote: > > >>thank you jakob, >> >>scarab tells me: >> >>"You do not have permission to view an issue with that ID. If you believe > > it > >>is a valid ID, check with the project owner or system administrator" >> >>any help? >> >>Sergey >> >>(I am associated with OJB module) >> >> >> >>-----Original Message----- >>From: Jakob Braeuchi [mailto:[EMAIL PROTECTED] >>Sent: Monday, March 22, 2004 2:16 PM >>To: OJB Users List >>Subject: Re: OJB report query >> >>hi sergey, >> >>ojb currently cannot handle multiple columns in one criteria. see >> >>http://nagoya.apache.org/scarab/issues/id/OJB242 >> >>jakob >> >>Manukyan, Sergey wrote: >> >> >>>Folks, >>> >>>I am repeating my question here as obviously it stands as a problem for me >>>now and either: >>>1. it cannot be solved by current OJB implementation >>>2. there is a solution I don't know about >>> >>>How can I specify expressions in OJB report query? >>> >>>F.e. I am making a report that as a column should produce addition of two >>>table columns : >>> >>>qry.setColumns( >>> new String[] { >>> "materialVariance + laborVariance" >>> } >>> >>>materialVariance and laborVariance are defined as field names in OJB >>>repository, unfortunately this code doesn't work as OJB failes to make a >>>mapping to actual table column names in SQL generation and makes SQL like: >>> >>>SELECT materialVariance + laborVariance FROM .... >>> >>>And of course there are no such columns in database table, >>>Now I am forced to make substitution and instead of field names include >>>column names in OJB query: >>> >>>qry.setColumns( >>> new String[] { >>> "MATVAR + LABVAR" >>> } >>> >>>Which is evidently a bad way of using OJB that is increasing future >>>maintenance. I am using RC4. >>> >>>Please tell me if there is or there is no solution for this problem in OJB >>>as it looks like limitation for me, >>> >>>Thank you, >>>-Sergey >>> >>> >>> >>> >>>********************** >>>** LEGAL DISCLAIMER ** >>>********************** >>> >>>This E-mail message and any attachments may contain >>>legally privileged, confidential or proprietary >>>information. If you are not the intended recipient(s), >>>or the employee or agent responsible for delivery of >>>this message to the intended recipient(s), you are >>>hereby notified that any dissemination, distribution >>>or copying of this E-mail message is strictly >>>prohibited. If you have received this message in >>>error, please immediately notify the sender and >>>delete this E-mail message from your computer. >>> >>>--------------------------------------------------------------------- >>>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] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ********************** > ** LEGAL DISCLAIMER ** > ********************** > > This E-mail message and any attachments may contain > legally privileged, confidential or proprietary > information. If you are not the intended recipient(s), > or the employee or agent responsible for delivery of > this message to the intended recipient(s), you are > hereby notified that any dissemination, distribution > or copying of this E-mail message is strictly > prohibited. If you have received this message in > error, please immediately notify the sender and > delete this E-mail message from your computer. > > --------------------------------------------------------------------- > 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]
