[JIRA] Resolved: (CAY-960) Incorrect logging when generated primary keys are used.

From: Michael Gentry (JIRA) ("Michael)
Date: Tue Jan 15 2008 - 15:25:33 EST

  • Next message: Michael Gentry: "Re: Logging changes?"

         [ https://issues.apache.org/cayenne/browse/CAY-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Michael Gentry resolved CAY-960.
    --------------------------------

        Resolution: Fixed

    Passed my test case, but want others to verify.

    > Incorrect logging when generated primary keys are used.
    > -------------------------------------------------------
    >
    > Key: CAY-960
    > URL: https://issues.apache.org/cayenne/browse/CAY-960
    > Project: Cayenne
    > Issue Type: Bug
    > Components: Cayenne Core Library
    > Affects Versions: 3.0
    > Environment: All
    > Reporter: Michael Gentry
    > Assignee: Michael Gentry
    > Fix For: 3.0
    >
    >
    > With the logging changes, an INSERT will incorrectly log the primary key column when the value is generated (auto-increment/identity). This value must be obtained from the database after the INSERT has completed. The current code prints this column, but shows the next parameter value, skewing the entire logged entry after the primary key.
    > For auto-generated keys on INSERT-only (show key value on DELETE, SELECT, UPDATE), do not show the auto-generated key in the log (since it doesn't exist yet). 

    -- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    This archive was generated by hypermail 2.0.0 : Tue Jan 15 2008 - 15:26:00 EST