| From: | Andreas <maps(dot)on(at)gmx(dot)net> | 
|---|---|
| To: | Andrej Ricnik-Bay <andrej(dot)groups(at)gmail(dot)com> | 
| Cc: | ListaPostgre <pgsql-novice(at)postgresql(dot)org> | 
| Subject: | Re: Need help with a function boolean --> text or array | 
| Date: | 2008-01-23 14:07:49 | 
| Message-ID: | 47974A35.8050802@gmx.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-novice | 
Andrej Ricnik-Bay wrote:
> On 23/01/2008, Andreas <maps(dot)on(at)gmx(dot)net> wrote:
>   
>> My view should look like this:
>> id, name, addons
>> ...
>> 11, 'Salami',  'Cheese, Salami'
>> 42, 'Fire',  'Cheese, Onion, Salami, Extra hot chilies'
>> ...
>>     
> Looks primarily like a normalisation problem to me.  I'd be
> going for a pizzaname-table, an ingredient-table and a pizza-table
> that combines these m:n and then worry about the view ...
>   
The pizza-table was a rather simplified example.
The real table is a questinnaire that has a number of single fields and 
some distinct groups of booleans.
For easy reading some of those boolean-groups should be rolled into one 
text field each but additionally every boolean should still appear as 
single column, too.
It wasn't my idea. I just do the dirty work.   ;)
Further normalisation would run me into crosstab issues and this is also 
a white spot for me.
Could you give me a sketch how a good design would represent such a 
questinnaire?
I understand the m:n approach.
My problem would rather be how to get a big view out of this m:n design.
The current design also is ambiguous in the aspect that the frontend-app 
just knows boolean as Yes/No so TRUE=Yes but FALSE could be No as well 
as Unknown.
Regards
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrej Ricnik-Bay | 2008-01-23 19:24:09 | Re: Need help with a function boolean --> text or array | 
| Previous Message | A. Kretschmer | 2008-01-23 10:12:59 | Re: using column alias to make operations |