On Tue, Sep 22, 2009 at 22:27, Isaac Wagner <[email protected]> wrote:
> I've hit the problem described in issue #61. Is there any sort of > workaround to this problem? It is possible to workaround the problem by not using the default collection, and using an alternate "class name" resolution mechanism, though that's a bit of work. > I'm stuck now and am not sure how to > proceed. Any chance this will be fixed soon? Thanks. Depends what you call soon. If nobody steps up to fix it, I'll probably fix it within a few months. 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. -- 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 -~----------~----~----~----~------~----~------~--~---
