This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, Since the lastest version; 24/02, when I add new row in database with a unitOfWork, the KeyTable value is not incremented automatically. This will cause duplicate values that throw an error in my case because of the primary key constraint. Have you any idea? My last build before this one is from 10/01. Thank you. |
|
|
|
|
We can't reproduce this here. Can you send us a repro? Also note that the KeyTable is incremented in batches. It will only be incremented when the IDs from the last batch run out. |
|
|
|
|
Sorry, I cannot take more time trying to correct this problem because it cost me 3 hours last Friday. The only thing that I can say is that I just install the latest build available, open again my visual studio and press f5 and immediately after the same existing code trying to insert a row in a table map with the keytable pattern, the keytable was not incremented. I uninstall the software and reinstall the previous one (20/01) and open again visual studio, press f5 and all is now ok. I don't know what I can sent to help you. Even if a simple demo works, my main business project don't works with the latest build. I was hoping that the same problem occurs for other. |
|
|
|
|
I've found it. There'll be a fix in the next nightly build. Many apologies for the inconvenience. |
|
|
|
|
Thank you very much. |
|
|
|
