Re: I need a pony: Model translations (aka "my proposal")

When using related table based approach for the translations, django could use pivoting to fetch all the translations with just one normal join. Some pseudo sql, skipping constrains and indexes... create table a ( id integer pkey ); create table b ( id integer pkey, a_id integer references

Re: I need a pony: Model translations (aka "my proposal")

Hi Gonzalo, > [...] sorry for the late answer. Sorry for my late answer, too. > I like your proposal! You simplified some over designed or complex > stuff about my original proposal and added some very neat ideas, good > work. Thanks! >> 4. Special case: Create an own model for translations

Re: I need a pony: Model translations (aka "my proposal")

2009/7/11 David Danier : > Hi Marc, hi Gonzalo, hi django-dev, [...] > So I thought about how model translations in django could work, and how > this should be used by the developer. I send this email directly to > Marc, because he is currently working on some

Re: I need a pony: Model translations (aka "my proposal")

Hi Veena, first sorry for my late answer, I missed your email somehow. The SomeObjTranslation-model is what should be dynamically created by some registry. This registry is a little more difficult than your suggestion, but should keep things simple enough:

Re: I need a pony: Model translations (aka "my proposal")

I think if it'd be possible to have only this syntax: from django.contrib.translations import translation translation.register(SomeObj, ['foo']) Veena On Aug 4, 9:45 pm, veena wrote: > Hi David, > I read your first post now. Then I think it could be great solution if >

Re: I need a pony: Model translations (aka "my proposal")

Hi David, I read your first post now. Then I think it could be great solution if it's possible to be implemented. Perhaps I appreciate less lines in every translation model. If you look at: class SomeObjTranslation(models.Model): language = models.CharField(max_length=5, \

Re: I need a pony: Model translations (aka "my proposal")

> I don't research your idea deeply but for first look it seems very > similar or same to django-multilingual. > http://code.google.com/p/django-multilingual/ >From the database perspective it is similar, meaning it uses the same database structure. What I tried to write down was mostly some

Re: I need a pony: Model translations (aka "my proposal")

I don't research your idea deeply but for first look it seems very similar or same to django-multilingual. http://code.google.com/p/django-multilingual/ Veena On 11 čnc, 16:51, David Danier wrote: > Hi Marc, hi Gonzalo, hi django-dev, > > I'm writing this email,

Re: I need a pony: Model translations (aka "my proposal")

> I have looked into the code and think implementing this should be > possible, but needs some changes in the django-ORM itself. I read some of the code around Queryset, Model Inheritance and the Query-object itself. I _think_ the parts where django needs some adjustments can be limited to two

Re: I need a pony: Model translations (aka "my proposal")

Hi David, I'm working on some other i18n parts right now, but I'll review your email before working on model translations. Thanks for sharing your idea, and I'll be back with comments soon. Cheers, Marc David Danier wrote: > Hi Marc, hi Gonzalo, hi django-dev, > > I'm writing this email,

I need a pony: Model translations (aka "my proposal")

Hi Marc, hi Gonzalo, hi django-dev, I'm writing this email, because I need some kind of future proof model translation in django in the near future. I tried many solutions and came up with two of my own (not released anywhere), but nothing seems to fit all needs translations might impose. So I