Re: DB design suggestion

2001-08-28 Thread Don Vawter
If you do it this way you will have to redesign your table every time you make some small change and it will be difficult to query the results (e.g. how many questions did people answer ). What happens when you add a 16th question. At a bare minimum I would make the following: 1. user table: > us

RE: DB design suggestion

2001-08-28 Thread Cornillon, Matthieu
I'm no expert on this. Nonetheless, here is my non-expert thinking: I'd keep all of the user information in one table. I would then create separate tables for payment, questions, text, image, sound, and video. This way, any "single" can have as many or as few payments/questions/etc., as they w