Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My collegues don’t like auto generated int serial number by database and want to use string primary key like :
“camera0001”
“camera0002”
As camera may be deleted, I can not use “total nubmer of camera + 1” for id of a new camera.
If you were me, how will you generate this kind of key in your program?
PS : I think auto generated serail number as primary key is OK, just don’t like arguing with my collegues.
I don’t agree that a sequence number is always the best key. When there is a natural primary key available, I prefer it to a sequence number. If, say, your cameras are identified by some reasonably short model name or code, like you identify your “Super Duper Professional Camera Model 3” as “SDPC3” in the catalog and all, that “SDPC3” would, in my opinion, be an excellent choice for a primary key.
But that doesn’t sound like what your colleagues want to do here. They want to take a product category, “camera”, that of course no one expects to be unique, and then make it unique by tacking on a sequence number. This gives you the worst of both worlds: It’s hard to generate, a long string which makes it slower to process, and it’s still meaningless: no one is going to remember that “camera0002904” is the 3 megapixel camera with the blue case while “camera0002905” is the 4 megapixel camera with the red case. No one is going to consistently remember that sort of thing, anyway. So you’re not going to use these values as useful display values to the user.
If you are absolutely forced to do something like this, I’d say make two fields: One for the category, and one for the sequence number. If they want them concatenated together for some display, fine. Preferably make the sequence number unique across categories so it can be the primary key by itself, but if necessary you can assign sequence numbers within the category. MySQL will do this automatically; most databases will require you to write some code to do it. (Post again if you want discussion on how.) Oh, and I wouldn’t have anyone type in “camera” for the category. This should be a look-up table of legal values, and then post the primary key of this look-up table into the product record. Otherwise you’re going to have “camera” and “Camera” and “camrea” and dozens of other typos and variations.