This is the one.
Father's last name prevails in each case. Very machista eh?
apellido_materno would be the "mother's name" in the English speaking
world, I believe (since mother's last name is her father's last name)
···
2006/1/2, Steve Litt <slitt@earthlink.net>:
On Sunday 01 January 2006 10:25 pm, Gerardo Santana Gómez Garrido wrote:
> We had a similar problem at work.
>
> In the Spanish speaking world we use two last names: one from the
> father's family (apellido paterno) and another from the mother's
> family (apellido materno). For the "first name" there's no limit in
> the number of names.
>
> Fortunately for us, the names were stored in the database as:
>
> <apellido paterno> <apellido materno> <nombres>
I've always wondered about this, both in Spanish names and American hyphenated
names. When the mother and father have a baby, does it go like this:
One reason is to be able to say things like "Who else lives on the
same street as this person" with a database query.
Another is that the Postal Service has a bunch of funky requirements
that must be met in order to qualify for discount mailing rates.
That being said, these days most big companies subscribe to an address
correction service, and just fix these things on the fly. Saves a lot
of hassle.
···
On 1/2/06, Christian Neukirchen <chneukirchen@gmail.com> wrote:
Wilson Bilkovich <wilsonb@gmail.com> writes:
> This reminds me of U.S. street addresses. I (on and off) do work that
> interfaces with a huge IBM mainframe application. That system has
> many, many separate fields for street addresses:
> Number, Direction, Street/Route, Quad, Suffix, Apartment, Line2, etc.
> I laughed at the way the original engineers had overbuilt. Ha ha ha.
> ...
> ...
> Then I had to write code that took a single address string and split
> it into its component parts, and I stopped laughing.
> e.g. 123 N. NESTOR LANE RD. SE #10B
>
> Life is complicated, it turns out.
And what's the point of storing that in different fields?
On 1/2/06, Kevin Brown <blargity@gmail.com> wrote:
On Monday 02 January 2006 01:28, Wilson Bilkovich wrote:
> This reminds me of U.S. street addresses. I (on and off) do work that
> interfaces with a huge IBM mainframe application. That system has
> many, many separate fields for street addresses:
> Number, Direction, Street/Route, Quad, Suffix, Apartment, Line2, etc.
> I laughed at the way the original engineers had overbuilt. Ha ha ha.
> ...
> ...
> Then I had to write code that took a single address string and split
> it into its component parts, and I stopped laughing.
> e.g. 123 N. NESTOR LANE RD. SE #10B
>
> Life is complicated, it turns out.
That's nothing. Addresses here are based on landmarks:
De donde fue Texaco Viejo 1/2 C al E, 2 c al S
City Name, Department name (sometimes), Nicaragua
Break that one up.
(literal translation is: From where the old texaco USED TO BE (it's a petronic
now), 1/2 a block to the east and 2 blocks to the south) That is just how
addresses are here.
And the only problems arise when one or both of paterno or materno is
itself composite and non hyphenated. Right, Gerardo?
In France, not only you *can* receive either your father's or mother's
family name, but you can change your family when you marry, divorce
remarry and so on.
And what's the point of storing that in different fields?
I'm working on a system that interfaces with a GIS mainframe system
(global information system?). It does street address / keymap ops for
police/fire. It requires that all fields are separate, including things
like street prefix, postfix, type, yada yada. A real pain.
Then I had to write code that took a single address string and split
it into its component parts, and I stopped laughing.
e.g. 123 N. NESTOR LANE RD. SE #10B
That's nothing. Addresses here are based on landmarks:
De donde fue Texaco Viejo 1/2 C al E, 2 c al S
City Name, Department name (sometimes), Nicaragua
Break that one up.
(literal translation is: From where the old texaco USED TO BE (it's a petronic
now), 1/2 a block to the east and 2 blocks to the south) That is just how
addresses are here.
And when you're geocoding it gets even worse. In the Rural US
you find lots of places where the mailboxes are at a different
location than the buildings (say, all mailboxes for a set of
farms centrally located for a group of farms); so geocoding for
emergency services should give different results than geocoding
for mail deliveries.
Nothing really on topic here, except re-iterating that the
original poster's request is a non-trivial problem.
···
On 1/2/06, Kevin Brown <blargity@gmail.com> wrote:
On Monday 02 January 2006 01:28, Wilson Bilkovich wrote:
