Hi all, I just commited a large update to the autodelay branch. Now I think that all those pesky corner cases about using belongs_to generated columns in an order_by or a constraint or what not should be solved (or at least trivially solvable).
Here is what I'm planning: unless someone can convince me otherwise, I'll merge the autodelay branch into the trunk with the explicit recommendation to not use the "autodelay feature" and use manual setup_all calls. The autodelay feature being just an ugly hack to ease transition. We might want to provide an option to deactivate the autodelay machinery altogether. I see that Jonathan has committed yesterday (r164) an improvement over statements. I had myself one in the works and just commited it to the autodelay branch. You might want to have a look at it Jonathan as I'm not sure both change don't collide. Here is my TODO list before 0.4: - merge the autodelay branch into the trunk - provide an option to deactivate autodelay. - resolve the assign_mapper problem (see other thread) - integrate beachcoder's "event" extension - more docs (especially regarding the autodelay stuff). I fear I'm the only one here who knows exactly what's the deal with that. If we can get Jonathon's improvements to the exisiting docs as well, that'd be really cool. Anything else I missed? -- Gaëtan de Menten http://openhex.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
