On 09/09/11 15:25 -0400, Phillip Heller wrote:
> On Sep 9, 2011, at 3:10 PM, Cédric Krier wrote:
>
> > Hi,
> >
> > I checked the module country_ar [1] and if I understand correctly you try
> > to get
> > some kind of autocompletion for the Argentina cities.
> >
> > First, I don't think it is good to extend the Subdivision to support cities,
> > especially because there is already a field in address to store the city and
> > it is not part of the ISO3166 nor ISO3166-2.
> >
> > So I (and Nicolas) thought about how we could provide a generic way to get
> > autocompletion on city (or other field in address).
> > Here are the result:
> >
> > - We need a place to store the combination of fields: zip, city, country,
> > subdivision.
> > - We must have autocompletion [1] on the fields zip and city.
> > - The system should learn from already encoding tuple.
> >
>
> Worth noting is that some locales in the United States (and I'm sure
> elsewhere) may have multiple city names for a zipcode.
>
> As an example:
>
> Denver, CO is 80233
> Thornton, CO is 80233
>
> The United States does have an extension to zip code ('plus 4') to
> disambiguate:
>
> Denver, CO is 80233-1248
> Thornton, CO is 80233-9822
>
> However, it is rare that one might know the "plus 4" for their location.
>
> Anyways, if you were planning to enforce uniqueness to the tuple, this might
> be a consideration.I don't want to enforce any uniqueness. We must never put such constraint if it doesn't respond to a requirement. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpiXG8WKRD3t.pgp
Description: PGP signature
