Yes, I could try.
Before embarking on this effort, though, I need clarification about a
documentation feature that I could not manage to reproduce:
>From Chapter 13 - I18n And L10n
-------
The symfony automations can make this much faster to write. If the
table containing internationalized data has the same name as the main
table with _i18n as a suffix, and they are related with a column named
id in both tables, you can omit the id and culture columns in the
_i18n table as well as the specific i18n attributes for the main
table; symfony will infer them. It means that symfony will see the
schema in Listing 13-7 as the same as the one in Listing 13-6.
-------
If the doc is correct, in principle the attributes would be implicit:
my_product:
-> _attributes: { isI18N: true, i18nTable: my_product_i18n }
my_product_i18n:
-> culture: { isCulture: true }
And the needed Product class's getName(), etc. methods would be
generated nevertheless
Your opinion?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---
