This could be sort of a FAQ. I skimmed this list but found nothing
appropriate.
I'm looking for a way to auto-generate translation (in the i18n sense)
tables for translatable columns to avoid writing the boilerplate, like in
(as probably everybody would do):
class WhatNot(Base):
...
class Language(Base):
...
class WhatNot_I18N(Base):
WhatNot_Id = Column(Integer, ForeignKey('WhatNot.Id'), primary_key=True)
Language_Id = Column(Integer, ForeignKey('Language.Id'), primary_key=True)
Description = Column(Unicode(128))
OtherText = Column(Unicode(128))
So for every WhatNot there would be one or more WhatNot_I18N for the
various translations of Description and OtherText.
I'm sure with SA there would be a way to automate creating such a
translation table on the fly when defining the master table, either with
@decorators, or like zzzeek's
"magic<http://techspot.zzzeek.org/2011/05/17/magic-a-new-orm>".
I've tried many ways, but to no success (well I've just started using it
for a few days). Has anybody succeeded in doing such a thing, or what would
be the best path towards it?
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/sqlalchemy/-/sSQaTyIbeikJ.
To post to this group, send email to sqlalchemy@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
