have a question regarding this patch: What is the right way to use PreparedStatements?.
is to UserPeer.doPSSelect() or change the peer.vm templates as suggested in an earlier post to do BasePeer.doPSSelect() from BasePeer.doSelect() ?. Basically in this approach, the user calls UserPeer.doSelect() which internally does a preparedStatement.. if this is the right/recommended way then I dont think that I can make a patch, since this would default to preparedstatements.. if the preferred approach is using UserPeer.doPSSelect(), then I will patch the peer.vm file. thanks and sorry for the delay in replying. -Subhash. --- John McNally <[EMAIL PROTECTED]> wrote: > On Thu, 2002-06-06 at 22:14, Subhash wrote: > > Found the problem: > > > > the sql that was being generated DID not contain the column names > > that were being extracted.. I just made overlooked that all along. > > > > For the regular doSelect calls, the addSelectColumns method is being > called. > > > > And that happens since the code generator, generates an overridden method > of > > the same signature, but in the case of the PSSelect methods, they are not > being > > overridden, and hence the columns are not being added. > > > > What would be the best way to fix this?. change the peer.vm to make this > > change, or are there any better ways to fix this problem?. > > > > patch Peer.vm > > john mcnally > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
