tag:support.appharbor.com,2010-11-23:/discussions/problems/3016-using-sequelizer-problemAppHarbor: Discussion 2012-03-13T18:09:17Ztag:support.appharbor.com,2010-11-23:Comment/144553402012-03-13T18:09:16Z2012-03-13T18:09:16ZUsing Sequelizer problem<div><p>Hi</p>
<p>You scenario would require overriding multiple connectionstrings
with different aliases and values. This is not currently supported.
Have you considered using the <a href=
"http://efmembership.codeplex.com/">Entity Framework Membership
provider</a> to unify your data model? If that's not an option, you
could specify the sequelizer connectionstring in a
Web.Release.config, but that's not recommended.</p>
<p>Michael</p></div>friism