Re: storing survey answers of different data types
From: Bob Badour <bbadour_at_pei.sympatico.ca>
Date: Fri, 24 Apr 2009 01:41:12 -0300
Message-ID: <49f142eb$0$5469$9a566e8b_at_news.aliant.net>
>
> Well, it's not me, the part-time mystic, I'd like to know how a system
> catalog/catalogue can signify the difference.
Date: Fri, 24 Apr 2009 01:41:12 -0300
Message-ID: <49f142eb$0$5469$9a566e8b_at_news.aliant.net>
paul c wrote:
> Bob Badour wrote:
>
>> paul c wrote: >> >>> Bob Badour wrote: >>> >>>> Joe Thurbon wrote: >>> >>> ... >>> >>>>> Just wondering, if one of the requirements for a system included >>>>> something like 'Be able to list all questionnaires', would >>>>> you still consider one-table-per-questionairre a reasonable design? >>>> >>>> Absolutely. It's a simple query from the system catalog. >>>> ... >>> >>> How do you tell the 'questionnaire' tables from the other tables? >> >> However you want.
>
> Well, it's not me, the part-time mystic, I'd like to know how a system
> catalog/catalogue can signify the difference.
Why does the system catalog have to signify the difference? One can create any relation one wants to identify them.
Seems to me that the
> system becomes the app, which would be okay by me. 'Catlog', all due
> respect to Codd, is not a very useful word. What's the point of ddl
> when dml could suffice? I think it is baggage, mostly due to the
> physical limits of thirty or more years ago. DBMS's would be different
> today if not for those, and thirty years from now, most developers
> won't even know and a few might start to think like the Mott's Clamato
> man. So there!
Huh? Received on Fri Apr 24 2009 - 06:41:12 CEST