Thanks for integrating the fix. I understand your justifications for leaving out the other tests. They were more for explanation or clarification. The reason I had the test_many_to_two is because my original problem contained two foreign keys into the same table, and I needed to eliminate that as a cause. I thought leaving the test case in since it did exemplify a particular pattern and wasn't covered already in the tests... and even though it didn't draw out any issues with the current code, could perhaps catch something in the future. That's your call, of course.
Thanks for forwarding the issue on to the SQLAlchemy project. That was my intention after I got some feedback here, so that saved me a stop. Michael responded, and based on his response, I created <a href="http://www.sqlalchemy.org/trac/wiki/UsageRecipes/ PropertyWithSameNameAsColumn">the SQLAlchemy recipe here</a> (http:// www.sqlalchemy.org/trac/wiki/UsageRecipes/PropertyWithSameNameAsColumn). I'd like to create an equivalent recipe in the Elixir docs, but I'm not quite sure yet what to do. Is there an existing mechanism for providing the child_fkey parameter to the properties when creating the mapper? Perhaps this pattern should be hard-coded into Elixir if the column name matches the attribute name. That is, if a class declares: column_name = ManyToOne(..., colname='column_name', ...) Elixir will detect the conflict and implement the child_fkey pattern as in the recipe above. Let me know your thoughts, and I'll be happy to provide a patch or recipe based on your direction. Regards, Jason On Apr 3, 4:59 am, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote: > On Thu, Apr 3, 2008 at 2:58 AM, Jason R. Coombs <[EMAIL PROTECTED]> wrote: > > > I've entered trac item #39 (http://elixir.ematia.de/trac/ticket/39). > > > I'd be interested in the developers' comments and any other > > suggestions. > > Your workaround stuff is applied now, but not the rest of the patch... > See the ticket for details... > > -- > Gaëtan de Mentenhttp://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 -~----------~----~----~----~------~----~------~--~---
