Allow user-specified Model base classes

[jfinkels]

This is in response to issue #62. It allows a user to specify a base class for models (which should be a subclass of flaskext.sqlalchemy.Model) in the constructor of flaskext.sqlalchemy.SQLALchemy. Note: this does not work with the SQLAlchemy.init_app(app) idiom unless the model class is specified in the constructor of SQLAlchemy.

[robcowie]

+1

[luaz]

+1

[hsk81]

+1

[klinkin]

+1

[wtf]

+1

[artnez]

+1

[glyphobet]

+1

[johaness]

+1

[jamesonjlee]

-1
you should do this with mixins and explicitly declare the inheritance for the new models instead.

# a contrive example 
def Base(object):
    def say_hello():
        print "hello"
def User(db.Model, Base):
    pass
me = User()
me.say_hello()

if you needed the db.Model inside the Base, that's a different thing.
I use this to create delete, get_or_create, etc methods with the models.

[lepture]

agree with @jamesonjlee . 👎

[davidism]

Extending this to allow other custom bases such as DeclarativeMeta, BaseQuery, etc. would be really useful. Right now I end up subclassing and overriding the extension to use custom classes.

[ThiefMaster]

👍 - this would still be increadibly useful and avoid nasty monkeypatching!

Using mixins instead is not a very good idea. You need to put them in every single model explictly even if you just want to add convenience methods which you do want in all your models.

[davidism]

#328