Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C41298.52089CB6"
Subject: Suggested Change to doDelete() in the Templates
Date: Thu, 25 Mar 2004 08:38:09 -1000
Message-ID: 
 <F436058E19EBD742A1F99DBFD1861830366773@NAWESMTHEX04VA.nadsuswe.nads.navy.mil>
Thread-Topic: Suggested Change to doDelete() in the Templates
Thread-Index: AcQSmFH2dfBd/bEwS1yReCwIYOSSww==
From: "Mitchell, Charles A CONT J6415," <charles.a.mitchell@pacom.mil>
To: <torque-dev@db.apache.org>

------_=_NextPart_001_01C41298.52089CB6
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm using Torque 3.1.

The doDelete() method in the Base[TableName]Peer class calls =
Base[TableName]Peer instead of [TableName]Peer.

Here's the code in BaseTableNamePeer :

public static void doDelete( Criteria criteria ) throws TorqueException =
{
  BaseTableNamePeer.doDelete( criteria, (Connection) null );
}

It should say :

public static void doDelete( Criteria criteria ) throws TorqueException =
{
  TableNamePeer.doDelete( criteria, (Connection) null );
}

I overrode doDelete( criteria, conn ) in TableNamePeer.  I did not =
override doDelete( criteria ).  So when I call TableNamePeer.doDelete( =
criteria ), it called the BaseTableNamePeer.doDelete( criteria, conn ) =
instead of the overridden method.

You get the picture.  A simple change to the templates fixed it.


------_=_NextPart_001_01C41298.52089CB6--