Re:Postgres sequences can skip 32 unexpectedly
by bluenose69 on Friday July 16, 2021 @11:59AM
(#27857670)
Years ago, I bought some software. Its serial number had quite a few digits. I found out later that I had been the first customer. I guess the idea was that customers might be more confident to jump in the water, if they saw others there already.
[ Parent
| on HN ]
Re:Postgres sequences can skip 32 unexpectedly
by eyelidlessness on Friday July 16, 2021 @02:50PM
(#27859785)
This is a technique used in other ways too. For instance, when opening a new checking account, it’s common to start with an arbitrary number for the first check. And often new businesses will start with an arbitrary invoice number.
Re:Postgres sequences can skip 32 unexpectedly
by jdofaz on Friday July 16, 2021 @05:29PM
(#27861454)
It used to be common for businesses to refuse to take a check if it had a low check number, the assumption was the account was new and had a higher chance of bouncing. Eventually the banks let you pick or set high numbers so you wouldn't have to deal with that inconvenience.
Re:Postgres sequences can skip 32 unexpectedly
by tyingq on Friday July 16, 2021 @04:09PM
(#27860676)
There's a fair number of ecommerce setups that default to numerically ascending order numbers also.
Re:Postgres sequences can skip 32 unexpectedly
by locao on Friday July 16, 2021 @02:06PM
(#27859226)
About 15 years ago I was part of a team of four developing a VoIP platform. When we were about to release we realized that our first customer would be upset if they knew they were actually the first customer. So each one of us said a number and our first user had an ID similar to 1003912 :)
Re:Postgres sequences can skip 32 unexpectedly
by imoverclocked on Friday July 16, 2021 @05:02PM
(#27861184)
I remember getting a large-ish IBM storage product 10-15 years ago with a serial number of 1. They actually updated it once someone realized!