I had some problems with replying to this message. I'm trying again, I hope I won't end up with two very similar messages posted.
Aidas Bendoraitis napisał(a): > The problem with this kind of translation implementation is that you > can't normally sort the translated items alphabetically. Actually you can, but it requires some work with querysets and gets complex quickly, especially when you want conditions like 'filter by the contents of Polish description if available and English otherwise'. Also, it would require patching Django to support left joins. I have a patch for that, but it is a quick hack, using syntax like Model.objects.filter(LEFTJOIN_othertable__field=value). > I would still propose the implementation that I suggested earlier: > http://groups.google.com/group/django-users/browse_frm/thread/e9545ee84a797e1b/de9ffbc0c79a3a17?lnk=gst&q=Aidas+Translatable&rnum=1#de9ffbc0c79a3a17 If I understand correctly, I implemented exactly what you described, storage-wise, with a different way to declare translatable fields. -mk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
