pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Aaron Bono <postgresql@aranya.com>
To: John Tregea <john@debraneys.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Joining a result set from four (4) tables
Date: Wed, 2 Aug 2006 13:01:57 -0500
Message-ID: <bf05e51c0608021101x617bf7eap519d2140e8b8c393@mail.gmail.com> (raw)
In-Reply-To: <44D02242.5050309@debraneys.com>
References: <44CDB1EF.6000508@debraneys.com>
	<bf05e51c0607310112wbc75fedkb21773c5bb64d11e@mail.gmail.com>
	<44CE9C63.7010409@debraneys.com>
	<bf05e51c0608011232jc6cae94wa82f3e6148766484@mail.gmail.com>
	<44D02242.5050309@debraneys.com>

On 8/1/06, John Tregea <john@debraneys.com> wrote:
>
>
> Because the logic structure of this software is in the front end
> application rather than the database there is a strong need to keep the
> naming of fields generic rather than specific, I am not using
> pre-defined foreign keys at all. If I was building the database with a
> purpose specific goal I would be doing what you say. I have found though
> that when I label elements at different levels of the back end for one
> purpose, they are less transportable in the long run. In this case the
> naming conventions are actually stored in another table and applied as
> aliases when needed. That way I can change the names and labels (for a
> new client or industry) while the underlying structure remains the same.
> I hope to increase interoperability in this way as well.



We all find ourselves in different situations and because of that, what
works for one person, doesn't work for another - so I understand.  Good luck
with the application and future queries.  Maybe you can use the existing
structure of your application to help create a query builder so you can have
it write a lot of your joins for you.  That should help avoid a lot of
simply typos or mix-ups when hand writing your queries.

I am glad the queries worked for you.

-Aaron

==================================================================
   Aaron Bono
   Aranya Software Technologies, Inc.
   http://www.aranya.com
==================================================================

view thread (7+ messages)  latest in thread

Message-ID: <bf05e51c0608021101x617bf7eap519d2140e8b8c393@mail.gmail.com>
Permalink:  ../bf05e51c0608021101x617bf7eap519d2140e8b8c393@mail.gmail.com/
Also on:    postgresql.org/message-id/bf05e51c0608021101x617bf7eap519d2140e8b8c393@mail.gmail.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: postgresql@aranya.com, john@debraneys.com
  Subject: Re: Joining a result set from four (4) tables
  In-Reply-To: <bf05e51c0608021101x617bf7eap519d2140e8b8c393@mail.gmail.com>

* 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