This is exactly what I had in mind :) I am installing python, svn, and Django on my personal machine and will do a couple of experiments regarding multilingual content at my spare time the next days.
Regards, Aidas Bendoraitis aka Archatas On 1/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Aidas Bendoraitis napisał(a): > > Replying to Marcin, I'll try to play around with JOINS this evening. > > Somewhy I believe that there is nothing complex with taking the > > different value if the necessary one doesn't exist -- maybe just one > > CASE WHEN, IF, or IFNULL. Or maybe the translation of the default > > language shouldn't be retrieved at all? Shouldn't the untranslated > > field just return an empty value and then the template could suggest a > > link to the original text reporting about the missing translation? > > On second thought, you are correct. Left joins let you > put all the translations in a single row and create an illusion > of one big table with translations in different columns, so you > can use any condition and operation you need. > > A short drive to a meeting was what I needed to look at > it from this perspective :) > > -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 -~----------~----~----~----~------~----~------~--~---
