<p dir="auto"><strong>Migrated issue, originally created by Anonymous</strong></p>
<p dir="auto">If we define many-to-many relation in base class with secondary table s1, and then re-define it with secondary table s2 in inherited class, it will try to use both relations and insert records in both s1 and s2.<br>
So in provided example we get<br>
deleted_posts -&gt; deleted_post_files &lt;- files AND deleted_posts -&gt; post_files &lt;- files, so object from base class with same primary index gets incorrectly associated to files table.</p>
<hr>
<p dir="auto">Attachments: <a href="../wiki/imported_issue_attachments/1477/sa_test3.py">sa_test3.py</a></p>
<p dir="auto"><strong>Migrated issue, originally created by paj (<a href="https://github.com/paj">@paj</a>)</strong></p>
<p dir="auto">The MSSQL module supports three different DBAPIs. It should be possible for the user to specify which one they want, ideally using a string, so this can be done from a framework's configuration file. Although there's code that tries to support this, it doesn't work at present, primarily because the MSSQLDialect.<strong>new</strong> doesn't see the constructor arguments, which would tell it which DBAPI to use.</p>
<p dir="auto">Fixing this may require a bit of a refactor, possibly beyond the MSSQL module.</p>