<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div><br><div><div>On Oct 4, 2014, at 1:10 AM, Kevin Benton <<a href="mailto:blak111@gmail.com">blak111@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Does sqlalchemy have good support for cross-database foreign keys? I was under the impression that they cannot be implemented with the normal syntax and semantics of an intra-database foreign-key constraint. </div></blockquote><div><br></div>cross “database” is not typically portable, but cross “schema” is. <div><br></div><div>different database vendors have different notions of “databases” or “schemas”.</div><div><br></div><div>if you can get the “other database” to be accessible from the target database via “otherdatabase.sometable”, then you’re in.</div><div><br></div><div>from SQLAlchemy’s perspective, it’s just a name with a dot. It’s the database itself that has to support the foreign key at the scope you are shooting for.</div><div><br></div><div><br></div><div><br></div><blockquote type="cite"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 3, 2014 at 5:25 PM, Ivar Lazzaro <span dir="ltr"><<a href="mailto:ivarlazzaro@gmail.com" target="_blank">ivarlazzaro@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Following up the latest GBP team meeting [0][1]:</div><div><br></div><div>As we keep going with our Juno stackforge implementation [2], although the service is effectively a Neutron extension, we should avoid breaking Neutron's migration chain by adding our model on top of it (and subsequently changing Neutron's HEAD [3]). If we do that, upgrading from Juno to Kilo will be painful for those who have used GBP. </div><div><br></div><div>There are roughly a couple of possibilities for reaching this goal:</div><div><br></div><div>1) Using a separate DBs with separate migration chain;</div><div>2) Using the same DB with separate chain (and different alembic version table).</div><div><br></div><div>Personally I prefer the option 1, moving to a completely different database while leveraging cross database foreign keys.<br></div><div><br></div><div>Please let me know your preference, or alternative solutions! :)</div><div><br></div><div>Cheers,</div><div>Ivar.</div><div><br></div><div><span>[0] <a href="http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-09-25-18.02.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-09-25-18.02.log.html</a></span></div><div><span>[1] <a href="http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-02-18.01.log.html" target="_blank">http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-10-02-18.01.log.html</a></span></div><div><span>[2] <a href="https://github.com/stackforge/group-based-policy" target="_blank">https://github.com/stackforge/group-based-policy</a></span></div><div><span>[3] <a href="https://review.openstack.org/#/c/123617/" target="_blank">https://review.openstack.org/#/c/123617/</a></span></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Kevin Benton</div>
</div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></body></html>