Re: Multilingual database - Mailing list pgsql-novice

From Terence Ng
Subject Re: Multilingual database
Date
Msg-id 20030514101118.52633.qmail@web41112.mail.yahoo.com
Whole thread Raw
In response to Re: Multilingual database  ("M. Bastin" <marcbastin@mindspring.com>)
Responses Re: Multilingual database
List pgsql-novice
Thank you very much for your patience.  May I have one
more question?

May I put the login and password of my customers in
the same table containing my customers name and
address?

Thanks in advance
Terence Ng

 --- "M. Bastin" <marcbastin@mindspring.com> wrote: >
At 11:12 AM +0800 5/13/03, Terence Ng wrote:
> >I see. Thank you very much.  But I have come up
> >another question.  For the language-dependent
> >information, there is a code to differentiate each
> >record, and every column has the same language.
>
>
> No!  One single column contains all descriptions,
> regardless of their language!
> If you'd have a column per language, then you'd get
> into the same
> kind of problems as when you'd have a table per
> language.
>
> Example:
>
> CODE    LANGUAGE    DESCRIPTION
> x123    French        frites surgeles
> x123    English        frozen french fries
> z456    French        gaufres belges
> z456    English        belgian waffles
>
> >  What
> >if I expand my web site, allowing customers from
> >different countries lookup their orders.  How do I
> >record their information if I allow them to
> register
> >their info in their languages?  For example, I will
> >have customer_id and customer_name.  How do I
> record
> >customer_name?  Is it a good practice if I create
> >every language a column, with customer_id as a
> >relation?
>
> Your customer data is probably not language
> dependent.  One table
> should be enough.
>
> Example:
>
> ID    LAST NAME    FIRST NAME    GENDER    LANGUAGE    ADDRESS
> 101    Dupont        Louis        m    French        ... France
> 102    Jones        Tina        f    English        ... USA
>
> The way you present this information on screen
> should be in the
> customer's language, but each bit of customer
> information you
> actually want to store, is unique per customer, and
> the language is
> not relevant: a last name is just always a last
> name, whether the
> person speaks French or English.
>
> Marc
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

_______________________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com.hk address at http://mail.english.yahoo.com.hk

pgsql-novice by date:

Previous
From: Katy Earl
Date:
Subject: Re: can't alter user with the postgres user
Next
From: "A.Bhuvaneswaran"
Date:
Subject: Re: Functions and triggers