I've made another update to the elixir trac ticket with another proposed patch. (see http://elixir.ematia.de/trac/ticket/39).
In short, while I agree with Gaëtan that there are several ways this issue could best be addressed (by extending the meaning of allow_column_override, by allowing for anonymous columns, or by explicitly managing property name conflicts), the currently prescribed practice for dealing with property name conflicts is to explicitly avoid them. My proposed patch attempts to do just that. I'm eager to hear your comments. Regards, Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
