undefined | Better HN

0 pointsdeveloper210y ago0 comments

>> we ended up with reservation_name

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.

0 comments

PeCaN10y ago

FFS, it's just reservation.reservation_name, it's not like he's parsing HTML with regular expressions or something. Like... big deal.

kbenson10y ago

I'm not sure if this is humor going over my head, or seriousness smacking me in the face.

davvolun10y ago

http://stackoverflow.com/questions/1732348/regex-match-open-...

vmasto10y ago

Could you elaborate on why this is so awful? (genuine question)

bottled_poe10y ago

I can think of a few reasons:

- 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.

developer2OP10y ago

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.

fleitz10y ago

Too much typing / line noise.

j / k navigate · click thread line to collapse