So... 1 minor issue I have noticed that might be on purpose is that when you manual override storage_name the version table still uses the class name to build the version table. I was kind of surprised by this, I figured at least I'd have a way of overriding it, but alas even in dm-more/next there is not currently a way of doing this. I'll probably patch it to call the parent tables storage_name rather than building using the class name.
The next issue is a compound issue. 1) When you make a STI table with is_versioned its version table will only have the same properties as the current table. So if you have a child that adds a new property then those properties aren't included in the version table. 2) As a result of 1, if a child adds a property and then you try to save it will give you an error when it tries to add the version because the table structures don't match. Has anyone else ran into the problems? Should I not expect to use is_versioned with STI? Is this a bug? it seems like a bug... I'll look into the issue some to see if I can't figure out a way to patch this and submit it to lighthouse. Ash --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
