On 6/25/07, remi jolin <[EMAIL PROTECTED]> wrote: > > le 23.06.2007 00:00 Gaetan de Menten a écrit: > > This is a (known) bug in Elixir. The cause is that we don't setup > > backrefs as we should. > > > > As I said to André Felipe Dias: > > ====== > > Feel free to work on a patch, though I'm not sure how hard it would > > be. Basically, when a relationship has an inverse, it must setup a > > backref. The catch is that you must catch all the arguments of the > > inverse relationship and pass them through to the backref. > > ====== > > > Gaetan, > > I made a (simple) patch and a test for backrefs. It seems to work (at > least as I expect it to work ;-) )
Great news! > I also found an issue in the test_multi.py test but I think it is a bug > in the test (I've corrected it also). I'll see about that. > The only test that does not pass is test_has_property but I think it > because my version of sqlalchemy is too old (0.3.6) "ImportError: cannot > import name column_property" Indeed. > How can we get further ? Please send the patch here and I'll have a look at it and commit it if it's good enough and otherwise tell you what's wrong. -- 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 -~----------~----~----~----~------~----~------~--~---
