You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by bu...@apache.org on 2001/09/22 19:44:13 UTC
DO NOT REPLY [Bug 3738] -
FooPeer.doDelete(Foo) doesn't work if Foo has multiple primary keys
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3738>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3738
FooPeer.doDelete(Foo) doesn't work if Foo has multiple primary keys
------- Additional Comments From dlr@finemaltcoding.com 2001-09-22 10:44 -------
Please add a stack trace.
BaseFooPeer.doDelete(Foo) is generated to build a Criteria object representing
the Foo it's deleting (via buildCriteria()), then hand off that Criteria to the
same BaseFooPeer.doDelete(Criteria) methods that are called when you create the
Criteria by hand. The only difference in the creation of the Criteria passed to
doDelete(Criteria) by doDelete(Foo) is a check whether the Foo being deleted is
new which results in whether PK values are added.
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org