I was using sqlite but that should not matter.
Now my concern is:
How to create Translation object , that can refer to multiple tables?,
how can I create copy of tables (schema) with only different table
name?
otherwords: How can I implement the solution with multiple Translation
tables (table
well i've no idea about scalability. it's just general
(semi-theoretical) OO approaches.
your approach with table-per-language seems faster... but how u make a
(switchable) pointer to a table? i'm not fluent in SQL, i dont know
if u can make the Book table point (foreignkey?) to some virtual
currency part:
i dont know if unified_price has to be in same table or in separate
one - or just a calculable property (non-db). maybe best is
calculable in separate table, with triggers or (ala
SQLAlchemyAggregator) mapperExt's to update it at every change of
appropriate rate and/or
I already implemented your solution:
Book : table with general data
id, isbn, category_id
BookTranslation: table with translations
id, book_id, title, language
Correct me if this is not what you meant
##
and this generally works up to 10k objects.
since I
