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! We are using the licensed version of LightSpeed (4.0.1136.19607 - dll version) For some reason an inserts in the table using unit of work doesn't update the KeyTable with a valid NextId. It always updates with the same NextId as it is presented already. We can't understand when this is appears. I've tested with 5+ version of LightSpeed and this is OK - no problems like that. We can't buy a new version right now, so we're looking for workaround with version we have. I've attached a sample project, that reproduces this thing. I ask you to help me solve that problem. |
|
|
|
|
A workaround for this is to set an explicit IdentityBlockSize property on the Table attribute for each entity, e.g.
|
|
|
|
|
Thank you! It solved the problem. But I don't understand why it solves... It seems like IdentityBlockSize default value is 0 in our current version :) I also tried to set this option to the context (LightSpeedContext |
|
|
|
|
Sorry Im not sure why this is the case either but when I had a look at the repro project setting the option on the context didn't work either. My suspicion is that given that nightly was from right after a commit which introduced the per table identity block sizes is that there was an error there which was subsequently fixed in a later build. If you can ping us at support at mindscape.co.nz then I can make a later set of runtime binaries available to you where this has been sorted.
|
|
|
|
