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/20 07:31:40 UTC

DO NOT REPLY [Bug 3738] New: - 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

           Summary: FooPeer.doDelete(Foo) doesn't work if Foo has multiple
                    primary keys
           Product: Turbine
           Version: 3.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Torque
        AssignedTo: turbine-dev@jakarta.apache.org
        ReportedBy: jon@latchkey.com


FooPeer.doDelete(Foo) doesn't work if Foo has multiple primary keys

If you construct the same query with a Criteria object, it works fine.

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org