You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by "Michael Gentry (JIRA)" <de...@cayenne.apache.org> on 2008/01/15 17:44:33 UTC
[JIRA] Created: (CAY-960) Incorrect logging when generated primary
keys are used.
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.
[jira] Closed: (CAY-960) Incorrect logging when generated primary
keys are used.
Posted by "Michael Gentry (JIRA)" <de...@cayenne.apache.org>.
[ https://issues.apache.org/cayenne/browse/CAY-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Gentry closed CAY-960.
------------------------------
Changing status from resolved to closed.
> 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.
[JIRA] Resolved: (CAY-960) Incorrect logging when generated primary
keys are used.
Posted by "Michael Gentry (JIRA)" <de...@cayenne.apache.org>.
[ 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.