I wasn't advocating making this connection "in general" (though I like the
autoconfigure option!), but only specifically for the case of reflection -
in this case, we know the DB supports it, and it would result in a better
python interface to the already existing tables.
On Thu, Jul 3, 2014 at 3
On 7/3/14, 6:15 PM, Mike Bayer wrote:
> On 7/3/14, 5:45 PM, Paul Molodowitch wrote:
>> I noticed that sqlalchemy now properly sets the onpudate / ondelete
>> properties of foreign keys when reflecting tables:
>>
>> https://bitbucket.org/zzzeek/sqlalchemy/issue/2183/support-on-delete-update-in-fore
On 7/3/14, 5:45 PM, Paul Molodowitch wrote:
> I noticed that sqlalchemy now properly sets the onpudate / ondelete
> properties of foreign keys when reflecting tables:
>
> https://bitbucket.org/zzzeek/sqlalchemy/issue/2183/support-on-delete-update-in-foreign-key
>
> However, it doesn't seem to set
I noticed that sqlalchemy now properly sets the onpudate / ondelete
properties of foreign keys when reflecting tables:
https://bitbucket.org/zzzeek/sqlalchemy/issue/2183/support-on-delete-update-in-foreign-key
However, it doesn't seem to set the cascade properties of relationships to
reflect th
