http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce Classic : DuplicateKey Error Thu, 11 Jun 2026 09:25:22 -700 Tue, 29 Jan 2008 10:39:13 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=625 http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2477#2477 Author: pkarsh
Subject: 625
Posted: 29-Jan-2008 at 10:39am

I'm afraid I don't understand your question. How would deleting the last record of a table cause you to lose the value entered in the NextId table? Are you trying to re-use primary keys of deleted records? We recommend against that. Under ordinary circumstances the Id generator and not end-users should be writing into the NextId table. If for some reason you cannot adhere to this rule, then I suppose you could put your SaveChanges call into a try-catch loop (which is a good idea anyway) and do something to handle a Save failure due to a Duplicate key error. If your primary keys are in ascending order, meaning, for example, that you would not assign a primary key of 3 after having assigned one of 4, then you might consider running a query to get the MAX value of the primary key column.

If you wish to send me a private email to explain your situation in more detail then click on the link to my user name and you will see a button that will enable you to do so.

Paul Karsh
IdeaBlade Support
]]> Tue, 29 Jan 2008 10:39:13 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2477#2477 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2476#2476 Author: aladdin
Subject: 625
Posted: 29-Jan-2008 at 9:29am

Dear Paul,

about your second opinion, if deleted the last record of Invoices then NextId table loose the serial number, and

the user must be have permission to modify the NextId table. Now, if the user is stupid maybe save wrong id in

the NextId table. In this case we get a duplicate key error.How can to protect ?

Thanks
]]> Tue, 29 Jan 2008 09:29:05 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2476#2476 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2271#2271 Author: pkarsh
Subject: 625
Posted: 19-Dec-2007 at 4:20pm

If you were to use the Verification engine to try to catch this error you would have to write your own custom verifier. In this case that would be quite complicated. That is probably not the right way to accomplish what you want to do.

If you are using the PooledNumericIdGenerator then in your NextId table you have to have an entry for the name of the table that you are doing Id generation for. If you have that then you should not get a duplicate key error.

Hope this helps.

Paul Karsh
IdeaBlade Support
]]> Wed, 19 Dec 2007 16:20:39 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2271#2271 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2256#2256 Author: aladdin
Subject: 625
Posted: 18-Dec-2007 at 2:15pm

When create new entity(on added before save)  the PersistenceManager use the PooledNumericIdGenerator class, to create primary key  to non AutoIncrement field and post it -1.Now, after save if created duplicated key how can the Verification engine to catch the error unfortunately used AdoHelper methods.

Thanks for all.
]]> Tue, 18 Dec 2007 14:15:40 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=625&PID=2256#2256