Tag Info

New answers tagged

0

My 2 cents, although I am not nearly as experienced as many of the others on this site. If it is related to data integrity (either from a relationship standpoint OR a standardized formatting standpoint), then I firmly believe that it should be handled by the database. If it's simply for a nice presentation, then I think that should be handled by the ...


0

I would always recommend to create constraints to prevent the insertion of wrong values. I don't see anything bad on it. It is just a little bit more work for the DBA but apart from preventing the insertion of invalid values it can also warn when it was about to happen letting the developer to correct his mistake, else it would be possible to have an ...


4

Based on your comment above, it sounds like when you said everything was stored in separate "databases", you actually meant to say "tables". I'm going to work with that assumption... I'd suggest a simple table that stores who's been invited to which event, and what their response was. invitations ----------- id (primary key for the table) user_ID ...


7

Please, don't store comma-separated lists in a single column. This is just a disaster waiting to happen. If these are separate facts, they should be stored separately. Table GroupMemberRoles GroupID FK UserID FK RoleID FK (PK on all three, with perhaps other constraints) Your queries (say, to find the admins of a certain group) should be of the ...



Top 50 recent answers are included