Bug 749467 - Failed Content Spec increments Content Spec ID
Summary: Failed Content Spec increments Content Spec ID
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ali Abbas
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-27 07:08 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-04 10:18:13 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2011-10-27 07:08:39 UTC
After three failed attempts... it succeeds, but with Content Spec ID 4??



Content Specification ID: 4
Revision: 5

[jwulf@gaura dumps]$ skynet pull --post -c 3
Skynet client version: 10.0
Loading configuration from /home/jwulf/.config/skynet.ini
Web Service at http://localhost:8080/ version: 10.0

INFO: No data was found for the specified ID!

Comment 1 Lee Newson 2011-10-28 00:38:47 UTC
That is a part of MySQL, it increments the AUTO_INCREMENT id outside of the transaction and only holds the lock until the end of the SQL statement.

Reference:
http://dev.mysql.com/doc/refman/5.1/en/innodb-auto-increment-handling.html

Comment 2 Ali Abbas 2011-10-28 02:18:08 UTC
This is fixed now, so we auto increment it our self inside the CSProcessor instead of using the database's AUTO_INCREMENT. It checks for the content spec Max ID then increments it by 1 once a valid content spec is processed.


Note You need to log in before you can comment on or make changes to this bug.