[development] relationships API vs i18n

Gabor Hojtsy gabor at hojtsy.hu
Fri Nov 10 13:59:49 UTC 2006

On Fri, 10 Nov 2006, Dries Buytaert wrote:
> On 09 Nov 2006, at 22:21, Gabor Hojtsy wrote:
>> We can of course introduce a new table into core to handle this just for 
>> i18n, and it would be very simple to do:
>> CREATE TABLE translation (
>> nid1 int
>> nid2 int
>>> ;
>> The problem is that it is too domain specific and not really forward 
>> looking IMHO. We might just end up with this, but we might get further if 
>> we think ahead.
> I don't see the addded value of doing this through a relationships API with a 
> generic table.  It would only safe 10 lines of code, and make things slower 
> and harder to grok.  Having simple, specialized tables (like the one above) 
> is anything but a bad thing, IMO.

OK, I am fine with a simple specialized solution.


More information about the development mailing list