[Flask] Add, Change and Delete Models during runtime with flask-sqlalchemy and flask-migrate

[Andrea D'Amore]

> On Sun, May 15, 2016 at 3:45 PM, Patrick Rieser <zufaellig at outlook.com>
> wrote:
>> The purpose of this is that it would be possible then to serve multiple
>> customers whose frontend overlaps mostly (the rest would be hidden behind
>> feature locks), but where the table layout differs significantly from, a
>> single application.

On 16 May 2016 at 17:17, Anthony Ford <ford.anthonyj at gmail.com> wrote:
> Would it not make more sense to run these as separate blueprints/apps?
> Dispatch to the appropriate blueprint and DB/model once logged in?

That's what sound reasonable from the need presented there.

> That seems like it would work for your application, and would require
> minimal re-writing/modding of the existing Flask/SQLAlchemy packages.

I'm still failing to see where that on-the-fly mapping chang is
needed, i.e. why not just restarting the app. Is it something done to
gain a more insightful understanding of the various components?


-- 
Andrea