Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalThe simplest method is to just ignore your perceived problem. Items that are in the database have an id, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an I’did that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
The simplest method is to just ignore your perceived problem. Items that are in the database have an id, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an I’d that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
The simplest method is to just ignore your perceived problem. Items that are in the database have an id, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an id that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
The simplest method is to just ignore your perceived problem. Items that are in the database have an I’did, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an I’d that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
The simplest method is to just ignore your perceived problem. Items that are in the database have an I’d, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an I’d that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
The simplest method is to just ignore your perceived problem. Items that are in the database have an id, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an I’d that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
The simplest method is to just ignore your perceived problem. Items that are in the database have an I’d, provided by the database. Items not in the database have no id. Both are valid states. “Insert” is not a valid operation if the item has an I’d that is not null. And “update” is an invalid operation if the item is not in the database.
You can decide whether id should be immutable - in that case adding an item to the database leads to the creation of a new item with the id changed.
