Re: A complex normalisation problem in MySQL 4.0.20 (innodb engine)

2005-03-21 Thread SGreen
symbulos partners <[EMAIL PROTECTED]> wrote on 03/21/2005 10:25:27 AM: > > I don't think so. You already have the country's name in it's own language > > on the countryToLanguage table, don't you? What name in which language is > > the "defaultName" column supposed to represent? If you can defin

Re: A complex normalisation problem in MySQL 4.0.20 (innodb engine)

2005-03-21 Thread symbulos partners
> I don't think so. You already have the country's name in it's own language > on the countryToLanguage table, don't you? What name in which language is > the "defaultName" column supposed to represent? If you can define what the > *contents* of that field is supposed to be, then you should be able

Re: A complex normalisation problem in MySQL 4.0.20 (innodb engine)

2005-03-21 Thread SGreen
symbulos partners <[EMAIL PROTECTED]> wrote on 03/21/2005 08:08:53 AM: > Dear friends > > we have a problem here. > > We have 3 tables > > - table language (id int not null auto_increment primarykey, languageName > tinytext) > - table country (id int not null auto_increment primarykey, defaul

A complex normalisation problem in MySQL 4.0.20 (innodb engine)

2005-03-21 Thread symbulos partners
Dear friends we have a problem here. We have 3 tables - table language (id int not null auto_increment primarykey, languageName tinytext) - table country (id int not null auto_increment primarykey, defaultName tinytext, defaultLanguage tinytext) - table countryToLanguage ((languageID int, coun