Skip to main content
Tweeted twitter.com/StackSoftEng/status/1102584643499556866
clarification
Source Link

Each customer has an ID. For every new customer it's incremented by 1.

My company is wanting to start selling to a new type of customer (lets call it customer B), and have their ID start at 30k on the same column.

Is this a poor design? Our system has an option to set the customer type, so there is no need for this. We're not expected to reach this number for our other type of customers until 2050 (it's currently at 10k).

I'm trying to convince them that this is a bad idea... It also doesn't help the third party company trying to implement this idea is ok with it.

Each customer has an ID. For every new customer it's incremented by 1.

My company is wanting to start selling to a new type of customer (lets call it customer B), and have their ID start at 30k.

Is this a poor design? Our system has an option to set the customer type, so there is no need for this. We're not expected to reach this number for our other type of customers until 2050 (it's currently at 10k).

I'm trying to convince them that this is a bad idea... It also doesn't help the third party company trying to implement this idea is ok with it.

Each customer has an ID. For every new customer it's incremented by 1.

My company is wanting to start selling to a new type of customer (lets call it customer B), and have their ID start at 30k on the same column.

Is this a poor design? Our system has an option to set the customer type, so there is no need for this. We're not expected to reach this number for our other type of customers until 2050 (it's currently at 10k).

I'm trying to convince them that this is a bad idea... It also doesn't help the third party company trying to implement this idea is ok with it.

Source Link

Auto incrementing from two different points on the same table?

Each customer has an ID. For every new customer it's incremented by 1.

My company is wanting to start selling to a new type of customer (lets call it customer B), and have their ID start at 30k.

Is this a poor design? Our system has an option to set the customer type, so there is no need for this. We're not expected to reach this number for our other type of customers until 2050 (it's currently at 10k).

I'm trying to convince them that this is a bad idea... It also doesn't help the third party company trying to implement this idea is ok with it.