| From: | "Chuck D(dot)" <pgsql-list(at)nullmx(dot)com> |
|---|---|
| To: | Jorge Godoy <jgodoy(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Geographic data sources, queries and questions |
| Date: | 2007-05-24 04:43:46 |
| Message-ID: | 200705232243.46928.pgsql-list@nullmx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday 23 May 2007 18:59, you wrote:
>
> I don't believe this is good design. You'll have to have a trigger or
> something to verify that the country_id+state_id on the city table are
> exactly equal to the country_id+state_id on the state table. If you
> don't, you might have something like (using US city names...) "country:
> USA -> state: NY" -> "country: Zimbabwe -> state: NY -> city: New
> York".
>
> It isn't a problem of "any country and any state" on the city table, but
> a problem of "this state inside that particular country". I'd drop the
> country column.
You are right, this is a bad design. The country_id on the city table has to
go.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-05-24 04:44:52 | Re: the future of pljava development |
| Previous Message | Guy Rouillier | 2007-05-24 04:43:43 | Re: the future of pljava development |