I have what I view as a hack of a workaround, but if you register the map builders
prior to issuing your DB calls, you should be fine. I've had to do this not only for
ordering, but also for duplicating objects for separate but identical databases (gen
Torque code for db "x" and then use all the code for DbName='y').
[Torque.registerMapBuilder("com.mycompany.om.map.MyObjectMapBuilder");]
On 9 Jul 2003 at 18:08, Geoff Fortytwo wrote:
> I'm having the problem as well. People have asked about this on this list a
> number of times, but no one seems to have an answer. The problem lies with
> using a string column for ordering vs any other column type. Try ordering
> with any other column which is not a string column. I'll bet it works.
>
> In the source code of BasePeer, it appears that the "db" variable is null.
> That variable is only referred to if the order by column is a string, so
> that's why there's a problem only when using string columns to order by.
>
> The value of db is set higher up in the function with:
> DB db = Torque.getDB(criteria.getDbName());
>
> So for some reason Torque.getDB is returning null.
>
> I've tried creating the Criteria using:
> Criteria crit = new Criteria();
> or
> Criteria crit = new Criteria("rego");
> where "rego" is my database name.
>
> I've tried calling
> crit.setDbName("rego");
>
> In my schema file I have the element
> <database name="rego" defaultIdMethod="none">
>
> But none of those things makes any difference.
>
> Can anyone help? Does anyone know how to fix this?
>
>
> At 01:50 PM 7/9/2003, Tim Clotworthy wrote:
> >Thanks for the reply. Did you ever resolve this, and if so, could you
> >tell me how? I am using Oracle9i database, and torque3.0. Thanks again.
> >
> > > -----Original Message-----
> > > From: Duddikunta, Padmanabha [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, July 09, 2003 4:32 PM
> > > To: 'Turbine Torque Users List'
> > > Subject: RE: Criteria.addAscendingOrderByColumn() bug?
> > >
> > > I have encountered same NullPointerException when ordering by
> >ascending as
> > > well as descending.
> > >
> > > Paddy
> > >
> > >
> > > -----Original Message-----
> > > From: Tim Clotworthy [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, July 09, 2003 4:22 PM
> > > To: [EMAIL PROTECTED] Apache. Org
> > > Subject: Criteria.addAscendingOrderByColumn() bug?
> > >
> > > Hello,
> > > I was hoping some could tell me whether there are any know bugs with
> >the
> > >
> > > org.apache.torque.util.Criteria. addAscendingOrderByColumn() method?
> > > I have a very simple query:
> > >
> > > FESCriteria crit = new FESCriteria();
> > >
> >crit.addAscendingOrderByColumn(RefTransactionCodesPeer.TYPE_OF_TRANSACTI
> > > ON);
> > >
> > > transList = (ArrayList) RefTransactionCodesPeer.doSelect(crit);
> > >
> > > If I leave out the addAscendingOrderByColumn line, it works fine. When
> > > included,
> > > I get an exception:
> > >
> > > java.lang.NullPointerException
> > > at
> > > org.apache.torque.util.BasePeer.createQuery(BasePeer.java:1209)
> > > at
> > > org.apache.torque.util.BasePeer.createQueryString(BasePeer.java:927)
> > > at
> >org.apache.torque.util.BasePeer.doSelect(BasePeer.java:1321)
> > > at
> > > com.hotapp.fes.om.BaseRefTransactionCodesPeer.doSelectVillageRecords(
> > > BaseRefTransactionCodesPeer.java:398)
> > > at
> > > com.hotapp.fes.om.BaseRefTransactionCodesPeer.doSelectVillageRecords(
> > > BaseRefTransactionCodesPeer.java:366)
> > > at
> > > com.hotapp.fes.om.BaseRefTransactionCodesPeer.doSelect(BaseRefTransac
> > > tionCodesPeer.java:334)
> > > at
> > > com.hotapp.fes.support.FESSupportDAO.selectTransTypes(FESSupportDAO.j
> > > ava:202)...blah, blah, blah..
> > >
> > > I have verified that the RefTransactionCodesPeer.TYPE_OF_TRANSACTION
> >is
> > > equivalent to a valid and appropriate String value, so its not that.
> > >
> > > Any ideas would be greatly appreciated. Thanks.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > 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]
