> Is it the case that the methods _never_ throw the exception regardless
> of targeted database?
hm, these methods just set single values in a torque "bean", sometimes a
dependend foreign object will be reset to null, eg.:
public void setAddressId(long v) throws TorqueException
{
if (this.addressId != v)
{
this.addressId = v;
setModified(true);
}
if (aAddress != null && !(aAddress.getAddressId() == v))
{
aAddress = null;
}
}
So i think the methods can never throw a TorqueException, because even with
a complex object model i can't see how these
methods could hit the database.
so long
Micha
> -----Original Message-----
> From: Dave Newton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 14, 2004 1:17 AM
> To: Apache Torque Users List
> Subject: RE: SetFkId throws TorqueException
>
>
> On Tue, 2004-04-13 at 17:16, Michael Manske wrote:
> > After a short look into several generated sources i have to
> agree with Alex,
> > imho these throws declarations are not neccessary for the mentioned
> > setSomeForeignKey() methods. I would appreciate if the
> declarations would be
> > removed with the next release.
>
> Is it the case that the methods _never_ throw the exception regardless
> of targeted database?
>
> Dave
>
>
>
> ---------------------------------------------------------------------
> 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]
