[CAY-329] Long vs. Integer PK

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1 [LEGACY], 1.2 branch
• Fix Version/s: 3.0M3
• Component/s: Core Library
• Assignee: Andrus Adamchik
• Reporter: Andrus Adamchik
• Created: 21/Jun/05 05:19
• Updated: 09/Nov/08 00:59
• Resolved: 16/Jan/08 09:29

Description

Test suite submitted by Mikaël Cluseau:

http://www.objectstyle.org/cayenne/lists/cayenne-devel/2005/06/0036.html

fails when an object is created, committed and then updated and committed. SQL UPDATE updates an ID value for no good reason. My investigation shows that this is due to Integer vs. Long PK... BIGINT PK columns default mapping is Long per JDBC standard. So on fetch it is converted to Long. PK generator on the other hand has a hardcoded behavior to create Integer ... So two values behave as if they are non-equal and generate a bogus update. We need to fix PK generator to use default JDBC to java mapping instead of assuming Integer.

Similar situation has been discussed before:

http://www.objectstyle.org/cayenne/lists/cayenne-devel/2005/03/0086.html

Issue Links

• is related to: CAY-643 Paginates queries are failing
• relates to: CAY-314 PK Generation Improvements

Sub-Tasks

• Change PK generator API to take PK DbAttribute parameter; generate pk based on DbAttribute type: Closed
• Update PK artifacts (AUTO_PK_SUPPORT and friends) to allow BIGINT values: Closed