On Fri, 27 Nov 2009 15:34:56 + Miguel Vaz said:
> Hi,
>
> This is my first post, and could use some points of view on the subject.
> Have a project that will have several languages for its records, for places,
> for example, whose names and descriptions will be in 3 languages.
>
> Have alrea
On Nov 27, 2009, at 6:17 PM, Miguel Vaz wrote:
> My 3rd option seems to be the most simple, although i admit it doesnt sound
> quite right. Having fixed table fields for languages doesnt seem correct.
Well, it all depends. If you need to add a column later, you need to do an
ALTER TABLE. In a p
My 3rd option seems to be the most simple, although i admit it doesnt sound
quite right. Having fixed table fields for languages doesnt seem correct.
I can see disavantages in all 3 options, thats why i wanted to ask
everybody's opinion on something like this, i mean, a assume that dealing
with a
I am really interested in the same answer...
I am making a script.. and as I will only have 2 languages I decided to use
you 3rd option (Fields for each language), because of less rows.
But I really would like to know if there is a better approach to this.
*eg. php function:*
function getRecipe
On Nov 27, 2009, at 4:34 PM, Miguel Vaz wrote:
> This is my first post, and could use some points of view on the subject.
> Have a project that will have several languages for its records, for places,
> for example, whose names and descriptions will be in 3 languages.
>
> Have already read several
Hi,
This is my first post, and could use some points of view on the subject.
Have a project that will have several languages for its records, for places,
for example, whose names and descriptions will be in 3 languages.
Have already read several sites about it but always end up with several
persp
