| From: | "Ian Sillitoe" <ian(dot)sillitoe(at)googlemail(dot)com> |
|---|---|
| To: | "Ted Byers" <r(dot)ted(dot)byers(at)rogers(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: (FAQ?) JOIN condition - 'WHERE NULL = NULL' |
| Date: | 2008-04-03 10:00:46 |
| Message-ID: | c6ff42340804030300i6846880dra7b62b116ae6211d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > We are annotating nodes on a hierarchical structure
> > where NULL implied an
>
> I don't mean to be rude, but yuck. Why provide a
> record for data that isn't there?
>
No offence taken - I'm trying to improve an old (partially inherited)
system, hence the original post.
I have no idea if this model would work for you, but
> maybe it will help.
>
That approach all sounds sensible, however going through the links that Richard
Broersma sent over in a previous post - I'm currently leaning towards the
flexibility and intuitive interface that ltree contrib module appears to
offer.
http://www.postgresql.org/docs/8.3/interactive/ltree.html
Cheers,
Ian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Sergio Borgonovo | 2008-04-03 10:28:43 | is it helpful for the optimiser/planner to add LIMIT 1 |
| Previous Message | Tom Dunstan | 2008-04-03 09:11:29 | Re: modules |