Re: Autogenerate ALWAYS assumes an empty schema with Oracle 11.2

My goodness! That was it! I created and used a standard user in Oracle and things worked as expected. Thanks a bunch. The more I run into some of these things, the more I dislike Oracle. Right on Michael, I learn, test, develop against Oracle XE because we use Oracle at work so I have to live

Re: [sqlalchemy] automap : problem with two relationships on same foreign key

On 01/03/2016 02:43 PM, yoch.me...@gmail.com wrote: > I've added theses lines here > > : > > | >

Re: [sqlalchemy] automap : problem with two relationships on same foreign key

there's actually two if you put your check everywhere it would be needed (I already tried when you first suggested that it warn, which is the origin of my response that this is not a one liner). the warning here is doable it just needs more state to be tracked as automap runs. if you want to

Re: [sqlalchemy] automap : problem with two relationships on same foreign key

Okay, I have one test failed for automap : ~/sqlalchemy $ ./sqla_nose.py test.ext.test_automap .E.. == ERROR: test.ext.test_automap.AutomapTest.test_relationship_explicit_override_m2o

Re: [sqlalchemy] automap : problem with two relationships on same foreign key

OK, thanks you. I think it's a good idea to issue a warning in such cases. Best regards Le samedi 2 janvier 2016 19:18:12 UTC+2, Michael Bayer a écrit : > > > > On 01/02/2016 11:38 AM, yoch@gmail.com wrote: > > Thank you. > > > > I hesitate between using this way, or explicitly specify

Re: [sqlalchemy] automap : problem with two relationships on same foreign key

On 01/03/2016 07:00 AM, yoch.me...@gmail.com wrote: > OK, thanks you. > > I think it's a good idea to issue a warning in such cases. unfortunately this is a difficult situation to detect since it is a valid use case to present a mapped class that already has relationships present on it, which

Re: [sqlalchemy] automap : problem with two relationships on same foreign key

I've added theses lines here : if relationship_name in map_config.properties: msg = "%s