If you try to add a policy group with the same policyGroupID as another one you will get a DB error since the policyGroupID is the primary key. The sync between the table and the sequence will be an issue if you've imported policy groups from somewhere else. The easiest fix is to drop and recreate the sequence:

drop sequence dmpolicygroup_seq;
create sequence dmpolicygroup_seq minvalue 100;

Assuming 100 is larger than the max policyGroupID used.  I believe as long as you only use the admin interface you should be OK.

--Kyle

Nathan Mische wrote:
My concern is that if we allow the createPolicyGroup method to assign the policyGroupID an existing policyGroup could be overwritten very easily. Also, how do we keep the DMPOLICYGROUP and DMPOLICYGROUP_SEQ tables in sync? For example, say I add a policyGroup with the policyGroupID of 70, do I then have to increment the DMPOLICYGROUP_SEQ multiple times to keep it in sync?
 
--Nathan

---
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to