On 7/16/07, Gaetan de Menten <[EMAIL PROTECTED]> wrote: > On 7/16/07, Jason R. Coombs <[EMAIL PROTECTED]> wrote: > > > > I've got a situation where I'm working with a legacy database that's > > defined in another project and some extensions to it, written in > > sqlalchemy. I'd like to use Elixir, but there appears to be an issue > > with autoloading some tables and referencing them with new ones. Here > > is a pure SQLAlchemy implementation that works: > > http://paste.turbogears.org/paste/1496 > > > > Here is the same implementation in SQLAlchemy/Elixir that fails: > > http://paste.turbogears.org/paste/1497 > > > > The error is in this traceback: http://paste.turbogears.org/paste/1498 > > > > The constraint.elements list is empty when constructing the Items > > object. I'm not sure what this means, because it gets into parts of > > sqlalchemy that I don't quite understand yet. > > > > I tried working around the problem by calling setup_all() after the > > autoloaded object was declared, but that did not help. > > > > I encounter the error with Elixir 0.3.0 and 0.4.0 (latest from svn > > this morning). > > > > Is this a strict limitation of Elixir or something for which a > > workaround or fix might be developed in the short term? > > This is a current limitation of Elixir. As always, this is a known > issue which I haven't had a real motivation to fix yet. I'll try to > fix that ASAP.
It was actually easier to fix than I expected. Should work now with latest trunk. -- 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 -~----------~----~----~----~------~----~------~--~---
