That is exactly what I was thinking. If there is at least one other person out there that agrees with me, then I think that it will be a valid design decision that can be explained in choices.txt.
As we do not have to provide any create functions the business level then there is nowhere to put this validation, unless you want to go to the trouble of creating extra methods in your facade that can never be called from the GUI and will not gan you any extra marks.
Originally posted by Jeremy Botha:
I was paranoid, and treated the combination of business name and location as a compound primary key; I didn't let users enter another company combination which matched a combination already existing in the database in order to enforce data integrity.
Originally posted by Romeo Kienzler:
Depending on your design you are overwriting existing data in your database!
Originally posted by rinke hoekstra:
I think that is a bad idea. A record in the urly bird database represents a ROOM. Why wouldn't a hotel owner be allowed to offer several rooms in his hotel? It could even be that a hotel has several rooms in the offering with exactly the same specs (size, smoking/non, etc).