pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Yury Don <yura@vpcit.ru>
To: pgsql-sql@postgresql.org
Subject: Re: weird structure
Date: Mon, 28 Aug 2000 09:49:00 +0600
Message-ID: <39A9E12C.CE30AB78@vpcit.ru> (raw)
References: <200008241824.e7OIOR528066@hub.org>
	<39A5E7A4.E928FC2C@vpcit.ru>
	<39A68D36.EADD6043@viafractal.com.br>

Renato De Giovanni wrote:
> 
> > > Consider the following tables/fields:
> > > table "person": fields "p_id", "p_name".
> > > table "person_attribute": fields "a_id", "a_name".
> > > table "person_data": fields "d_person_id", "d_attribute_id",
> > > "d_value".
> > >
> > > Also consider that a person may not have data related to all possible
> > > attributes.
> > >
> > > Using this structure, how could I retrieve in one row with a single
> > > select statement all attributes from a person (showing null to
> > > attributes that were not registered to him)?
> > >
> > > Thanks for any suggestion,
> > > --
> > > Renato
> > > Sao Paulo - SP - Brasil
> > > rdg@viafractal.com.br
> >
> > I did similar things using the following technique:
> > in frontend I gather all attributes from person_attribute and then
> > generate a query like this:
> >
> > select *, (select distinct d_value from person_data where d_person_id =
> > person.p_id and
> > d_attribute_id = 'here first attribute id'), (select distinct d_value
> > from person_data where d_person_id = person.p_id and d_attribute_id =
> > 'here second attribute id'), ... from person
> > --
> > Sincerely yours,
> > Yury
> 
> Yury...
> That worked perfectly! Thank you very much!
> 
> Tell me, I've never seen this sql construction before, is it specific to
> postgres? Or should it also work on other databases?
> 
> And is there any relevant performance issue considering this kind of
> database schema and its peculiar sql commands?
> 
> Thanks again!
> --
> Renato
> Sao Paulo - SP - Brasil
> rdg@viafractal.com.br

This construction works in any database which support subselect in
target list in "select" statement, for example I used this in Interbase.
What about performance - it strongly depends on amount of attributes. In
order to maximize it you need to create indexes on all fields which
participate in "where" clause - p_id, d_person_id, d_attribute_id. And
performance .

-- 
Sincerely yours,
Yury



view thread (6+ messages)

Message-ID: <39A9E12C.CE30AB78@vpcit.ru>
Permalink:  ../39A9E12C.CE30AB78@vpcit.ru/
Also on:    postgresql.org/message-id/39A9E12C.CE30AB78@vpcit.ru

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: yura@vpcit.ru
  Subject: Re: weird structure
  In-Reply-To: <39A9E12C.CE30AB78@vpcit.ru>
  References: <200008241824.e7OIOR528066@hub.org> <39A5E7A4.E928FC2C@vpcit.ru> <39A68D36.EADD6043@viafractal.com.br> <39A9E12C.CE30AB78@vpcit.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox