That's absolutely terrifying. You've just provided my subconscious with new material with which to populate my nightmares.
How did the code using that database operate? Were you using "reservation_name", or did the application revert the naming scheme by mapping the column to "name"?
- The field name implies that the primary key field is a string. This entails numerous issues (eg. How do you generate a new unique ID?)
- It is not obvious that the field is the primary key.
- A 'name' property on a reservation doesn't make sense. Is it the name of the person making the reservation? How can this be unique? etc.
My use of "name" was a poorly chosen example to tie to the concept of a reservation. I just chose it because "name" is an extremely common and unambiguous column in many tables.
That's absolutely terrifying. You've just provided my subconscious with new material with which to populate my nightmares.
How did the code using that database operate? Were you using "reservation_name", or did the application revert the naming scheme by mapping the column to "name"?
Either way, FML.