Re: (FAQ?) JOIN condition - 'WHERE NULL = NULL'
| От | Ian Sillitoe |
|---|---|
| Тема | Re: (FAQ?) JOIN condition - 'WHERE NULL = NULL' |
| Дата | |
| Msg-id | c6ff42340804021233p321a9c85rf41cc1f9ea4f9e6b@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: (FAQ?) JOIN condition - 'WHERE NULL = NULL' ("Richard Broersma" <richard.broersma@gmail.com>) |
| Список | pgsql-general |
Thanks very much for this and to all the reponses. As a side note, I've only joined this mailing list this afternoon, but it already seems like an good choice (albeit one I should have made about 2 years ago :P) - very active and very helpful - excellent work, many thanks indeed.
Cheers,
Ian
Cheers,
Ian
On Wed, Apr 2, 2008 at 8:08 PM, Richard Broersma <richard.broersma@gmail.com> wrote:
On Wed, Apr 2, 2008 at 11:43 AM, Ian SillitoeThere are a couple of choice you can use:
<ian.sillitoe@googlemail.com> wrote:
> I completely take your points - so maybe I should be asking for advice on
> database design instead.
First is the PostgreSQL contribe Module Ltree:
http://www.postgresql.org/docs/current/static/ltree.html
There is the common adjancy list model:
http://www.sqlsummit.com/AdjacencyList.htm
Celko's Nested set model: { probably provides the most functionality
but with hi costs for INSERT/UPDATE ops)
http://www.intelligententerprise.com/001020/celko.jhtml
and Lastly the Path enurmation model:
http://www.onlamp.com/pub/a/onlamp/2004/08/05/hierarchical_sql.html
One of these model should hopefully be a best fit for you.
--
Regards,
Richard Broersma Jr.
В списке pgsql-general по дате отправления: