With OD 6.0.1 (with delete tracker enabled), I'm testing stuff and consequently, redeploying the same record many times. However, every other time, it likes to DELETE the record just after inserting it. I've never noticed this type of bizarre behavior from OD and I hope it's just something I'm doing wrong, but here's part of the log to show you what I mean:
DD:INSERT INTO CONTENT_PRESSRELEASES(title,summary,file_name,file_year,submit_date,effective_date,expiration_date) VALUES (?,?,?,?,?,?,?)
DD:Column: title, field: Headline, Index: 1,Converting 'new press release' to STRING
DD:Column: summary, field: Body, Index: 2,Converting 'qwdqwegwegre rewgre refref wefwe ewfwef' to STRING
DD:Column: file_name, literal: Development_Guidlines.doc, Index: 3,Converting 'Development_Guidlines.doc' to STRING
DD:Column: file_year, literal: 2006, Index: 4,Converting '2006' to STRING
DD:Column: submit_date, literal: 04/27/2006, Index: 5,Converting '04/27/2006' to TIMESTAMP
DD:Column: effective_date, field: StartDate, Index: 6,Converting '4/25/2006' to TIMESTAMP
DD:Column: expiration_date, field: EndDate, Index: 7,Converting '5/25/2006' to TIMESTAMP
DD
ELETE FROM CONTENT_PRESSRELEASES WHERE title = ? AND effective_date = ? AND expiration_date = ? AND file_name = ? AND file_year = ? AND submit_date = ?
DD:Column: title, field: null, Index: 1,Converting 'new press release' to STRING
...
Pretty straight-forward, right? In fact, a classic use of content management. Anyway, WHY would it delete the record that it just inserted? I understand if it's trying to delete the duplicate but it winds up deleting both occurances at one time. This table, by the way, has a auto incremented primary key which the DB is maintaining. TeamSite does have any concept of what that value is so it's not in its schema (maybe that's my problem). Instead, I'm defining the primary key as a joint key among three fields in the db schema.
So, what's the deal?
