Andreas Ntaflos <[EMAIL PROTECTED]> wrote: > My problem statement remains partially valid, though. > Auto-incrementing the roomID in the Room table would make each room > have its very own room number but the primary key still would need to > consist of both buildingID and roomID
Why? > or else the modelling of a room > as a weak entity wouldn't work correctly. Define "weak entity". Precisely what properties does it have that are not represented in the model? > The buildingID is still a > foreign key so SELECTing all rooms of one particular building is > still possible but that's only part of the conceptual model. In what way having a unique roomID violates your conceptual model? > I suppose it's not something the authors of books on database systems > would approve of. To the best of my knowledge, they are not the ones paying my salary, so personally I'm not too worried about their disapproval. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
