On Thu, Sep 24, 2009 at 16:53, Isaac Wagner <[email protected]> wrote:
>> If you care about this problem, you could also ask the migrate team >> why they put that "reload" line in their code when it's notorious one >> shouldn't rely on it (and from a very quick look at their code, I'm >> not even sure it is useful). I meant to discuss this with them for >> months now but well... never took the time to do so. Of course, Elixir >> should also behave correctly in that case, but still... if it was >> fixes on their side, that'd be good too. > As an experiment I downloaded the source code to migrate and commented > out the "reload" line. From what I could tell that might have > actually worked, except that I found out that migrate does not support > MSSQL. So, at this point I'm left to do a manual migration of the > database. What a pain. For future reference (it won't help you since it doesn't help you overcome the MSSQL issue), there *is* a very simple workaround to making Elixir work with migrate: you only need to add a "cleanup_all()" line in your module defining your entities, before you declare them. I wonder why I didn't think of something that simple sooner... -- 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 -~----------~----~----~----~------~----~------~--~---
