RE: [babel-dev] Translations and Project Versions

["Mike Milinkovich" <mike.milinkovich@xxxxxxxxxxx>]

 

I know I’m just the pointy-haired boss here, but in my experience lack of flexibility in schema is always regretted in the end.

 

So I’m a “0” vote on this approach.

 

Neat trick, but doesn't this mean that the user can either "replace ALL other versions of this string with this new translation" or "replace NO other versions of this string..." - there's no middle ground?  But, actually, that doesn't seem like a big restrictions - I like this solution.

Denis Roy wrote:

I actually put some thought into this, and I think you can get away with it in a fairly efficient manner without creating a table.  I simply replaced the single 'INSERT INTO translations' SQL query with: