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
|
I am using Lightspeed 2.2. Since a few days I have been noticing big jumps in the keys that are being generated. It started around 48000 and now seems to jump by 20000 about every day. Could it be that there is a problem with large numbers? |
|
|
|
|
Hi Frank, We are not aware of any issues? Can you elaborate on what you are seeing and also are you using a custom identity block size?
|
|
|
|
|
No we're not setting the value, so we're using the default of 10. Today there was a jump of 800, from 246762 to 247561. It could be a bug of ours of course, but our test system does not behave this way. |
|
|
|
|
Are you able to using a profiling tool or attach a logger to capture the SQL? This will confirm what LightSpeed is doing in regards to the block reservations from KeyTable.
|
|
|
|
|
Excellent idea. Actually, I found out that the query log is enabled on our server, but it seems to only log SELECT statements, not UPDATE. I'll try to pursue this further. |
|
|
|
|
UPDATE: I figured it out. I had a table (created from a CSV file) that had an ID field that always contained zero. Some interaction between my code and LightSpeed seems to have caused new IDs to be allocated whenever records were read from that table. After replacing the ID field with non-zero values, the problem seems to have gone away. |
|
|
|
