From: | "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-sql(at)postgreSQL(dot)org |
Subject: | RE: [SQL] Odd "problem", not sure if there is a solution .... |
Date: | 1999-03-26 16:29:17 |
Message-ID: | D05EF808F2DFD211AE4A00105AA1B5D20371DA@cpsmail.cpsgroup.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
It's possible, but not on the SQL end. You'll have to do the work on the
display end. If you're using PHP or Perl I'd be happy to give you a hand.
-DEJ
> -----Original Message-----
> From: The Hermit Hacker [mailto:scrappy(at)hub(dot)org]
> Sent: Thursday, March 25, 1999 9:47 PM
> To: pgsql-sql(at)postgreSQL(dot)org
> Subject: [SQL] Odd "problem", not sure if there is a solution ....
>
>
>
> am working up a database for client that contains answers for online
> testing...right now, the 'tables' look like:
>
> userid Q1 Q2 Q3 Q4 Q5 Q6 Q7 etc
>
> I want to change it so that its more generic, as:
>
> userid question_no answer
>
> so that instead of one row per user, there are X rows...
>
> the problem is that, somehow, I want the client to be able to view the
> results as the first format (ie. one line per user) with it
> being stored
> as multiple lines per user...
>
> Possible?
>
> Marc G. Fournier ICQ#7615664
> IRC Nick: Scrappy
> Systems Administrator @ hub.org
> primary: scrappy(at)hub(dot)org secondary:
> scrappy(at){freebsd|postgresql}.org
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | secret | 1999-03-26 20:08:13 | Re: [SQL] Odd "problem", not sure if there is a solution .... |
Previous Message | Oleg Broytmann | 1999-03-26 09:54:27 | Re: [GENERAL] Re: [SQL] sql 92 support in postgres |