Autonumbering and support

[sten]

First of all:

I would normally have sent this question to support, but for some reason the "Support Requests" page does not allow me to make a new ticket.

I do have active support, but the webpage says:

"Attention: 
The product previously saved as your default, [Product + Release + Language Installed], is no longer on Subscription. Please re-select below. "

When I try to find my product in the "Product" or "Release" combo/search box I always get "No results matched"

My real issue:

I have a few workspaces that uses SQL autonumbering. They have been working as expected for the last couple of years.

 >> (AUTONUMBER('CR-', NUMBER__AUTO_INC, 5)) <<

Today QA asked me why some of these workspaces had started to skip numbers. One workspace had skipped from 00040 to 00073.

There are no deleted records in the workspace. Does anyone have an idea?

[owais.zahid · Accepted solution]

NUMBER__AUTO_INC is a sequence. Sequence ensures the ordering but doesn't guarantee gap free sequence. There can be many reasons for it, the most common one is the transaction rollback. This behavior is consistent across various RDBMS. 

[sten]

Ok, now I have a reasonable explanation.

I was just curious to why it happened. We have had Fusion for 3-4 years and this is the first time something like this happened.

Also, I was pretty sure that it was not something we caused because only a very few people use these particular workspaces.