flask-sqlalchemy or sqlalchemy

Question

I am new in both flask and sqlalchemy, I just start working on a flask app, and I am using sqlalchemy for now. I was wondering if there is any significant benefit I can get from using flask-sqlalchemy vs sqlalchemy. I could not find enough motivations in http://packages.python.org/Flask-SQLAlchemy/index.html or maybe I did not understand the value!! I would appreciate your clarifications.

Solution 1

The main feature of the Flask-SQLAlchemy is proper integration with Flask application - it creates and configures engine, connection and session and configures it to work with the Flask app.

This setup is quite complex as we need to create the scoped session and properly handle it according to the Flask application request/response life-cycle.

In the ideal world that would be the only feature of Flask-SQLAlchemy, but actually, it adds few more things. Check out the docs for more info. Or see this blog post with the overview of them: Demystifying Flask-SQLAlchemy (update: the original article is not available at the moment, there is a snapshot on webarchive).

When I first worked with Flask and SQLAlchemy, I didn't like this overhead . I went over and extracted the session management code from the extension. This approach works, although I discovered that it is quite difficult to do this integration properly.

So the easier approach (which is used in another project I am working on) is to just drop the Flask-SQLAlchemy in and don't use any of additional features it provides. You will have the db.session and you can use it as if it was pure SQLAlchemy setup.

Solution 2

Flask-SQLAlchemy gives you a number of nice extra's you would else end up implementing yourself using SQLAlchemy.

Positive sides on using Flask-SQLAlchemy

---

1. Flask_SQLAlchemy handles session configuration, setup and teardown for you.
2. Gives you declarative base model that makes querying and pagination easier
3. Backend specific settings.Flask-SQLAlchemy scans installed libs for Unicode support and if fails automatically uses SQLAlchemy Unicode.
4. Has a method called apply_driver_hacks that automatically sets sane defaults to thigs like MySQL pool-size
5. Has nice build in methods create_all() and drop_all() for creating and dropping all tables. Useful for testing and in python command line if you did something stupid
6. It gives you get_or_404()instead of get() and find_or_404() instead of find() Code example at > http://flask-sqlalchemy.pocoo.org/2.1/queries/

Automatically set table names. Flask-SQLAlchemy automatically sets your table names converting your ClassName > class_name this can be overridden by setting __tablename__ class List item

Negative sides on using Flask-SQLAlchemy

---

1. Using Flask-SQLAlchemy will make add additional difficulties to for migrating from Flask to let's say Pyramid if you ever need to. This is mainly due to the custom declarative base model on Flask_SQLAchemy.
2. Using Flask-SQLAlchemy you risk using a package with a much smaller community than SQLAlchemy itself, which I cannot easily drop from active development any time soon.
3. Some nice extras Flask-SQLAlchemy has can make you confused if you do not know they are there.

Solution 3

To be honest, I don't see any benefits. IMHO, Flask-SQLAlchemy creates an additional layer you don't really need. In our case we have a fairly complex Flask application with multiple databases/connections (master-slave) using both ORM and Core where, among other things, we need to control our sessions / DB transactions (e.g. dryrun vs commit modes). Flask-SQLAlchemy adds some additional functionality such as automatic destruction of the session assuming some things for you which is very often not what you need.

Solution 4

The SQLAlchemy documentation clearly states that you should use Flask-SQLAlchemy (especially if you don't understand its benefits!):

[...] products such as Flask-SQLAlchemy [...] SQLAlchemy strongly recommends that these products be used as available.

This quote and a detailed motivation you can find in the second question of the Session FAQ.

Solution 5

As @schlamar suggests, Flask-SqlAlchemy is definitely a good thing. I'd just like to add some extra context to the point made there.

Don't feel like you are choosing one over the other. For example, let's say we want to grab all records from a table using a model using Flask-Sqlalchemy. It is as simple as

Model.query.all()

For a lot of the simple cases, Flask-Sqlalchemy is going to be totally fine. The extra point that I would like to make is, if Flask-Sqlalchemy is not going to do what you want, then there's no reason you can't use SqlAlchemy directly.

from myapp.database import db

num_foo = db.session.query(func.count(OtherModel.id)).filter(is_deleted=False).as_scalar()

db.session.query(Model.id, num_foo.label('num_foo')).order_by('num_foo').all()

As you can see, we can easily jump from one to the other with no trouble and in the second example we are in fact using the Flask-Sqlalchemy defined models.

View more solutions

Comments

[schlamar]

Yes, in your use case Flask-SQLAlchemy seems obsolete. But if the OP would have such a scenario he probably won't ask this question. For a new user who don't know anything about session scope Flask-SQLAlchemy is definitely a must!

[pmav99]

Flask-sqlalchemy seems to be unmaintained. The last update was on 1st of August of 2013. Is this advice relevant any more?

[schlamar]

@pmav99 as long as you do not have concrete issues with it I would still recommend it, especially for new users.

[Steve Bennett]

Seems to be actively maintained as of November 2014. Lots of recent commits. github.com/mitsuhiko/flask-sqlalchemy/commits/master

[Markus Meskanen]

Even though OP didn't ask it directly, imo. he wanted to know the benefits of Flask-SQLAlchemy. Your answer is literally "use it even if you don't know what the benefits are" -- yes, what are the benefits?

[Markus Meskanen]

"For example lets say we want to grab all records from a table using a model using Flask-Sqlalchemy. It as simple as Model.query.all()" -- this can all be done with just SQLAlchemy, using Flask-SQLAlchemy provides absolutely nothing new here.

[Mark Amery]

I remain confused. The linked blog post (and official docs!) list some plain SQLAlchemy features (like the declarative base) as if they are Flask-SQLAlchemy features; it's unclear whether they're taking credit for stuff built into SQLAlchemy or they've reimplemented it (nor why they did so, if it's the latter). Your first paragraph lists two features: convenience wrappers for session management (but won't you need to roll your own anyway if you want to use your SQLAlchemy models outside Flask?) and some unspecified "configuration" to "work with the Flask app". What does that mean?

[Jeff Bluemel]

you are awesome! I stumbled upon this post and it solved a problem I was having. after I installed anaconda, for some reason normal updates were not working. changed from Model.query.all() to db.session.query(Model).all() for some reason allowed the sessions to track and updated as normal.

[Boris Serebrov]

I am also a bit confused by questions. The linked blog post is quite clear IMO, for example, it says "Custom declarative base model with support for query property and pagination" the key is "custom" and "with support for query property and pagination" is what it adds on top of SQLAlchemy's declarative base.

[Boris Serebrov]

Regarding the "convenience wrappers" - they are not for convenience, but to make things work properly. To start using SQLAlchemy you need the database connection (eninge / connection / session) objects and you don't want to create these each time you need to make an SQL query, so these should be created globally and avaiaiable across the application code. So you can do something like "from yourapplication import db" and then do "db.session.something()" without thinking how to create and initialize this "db" object properly.

[Boris Serebrov]

And regarding the unspecified "configuration" to "work with the Flask app" - it is actually specified in the second paragraph: This setup is quite complex as we need to create the scoped session and properly handle it according to the Flask application request/response life-cycle. See more details in the SQLAlchemy docs: When do I construct a Session, when do I commit it, and when do I close it? and Contextual/Thread-local Sessions.

[mbadawi23]

This answer does not answer the OP's question. You are recommending flask-sqlalchemy, whithout providing much reasoning behind the recommendation.

[schlamar]

Because this is already covered in the link to the SQLAlchemy documentation...

[tabebqena]

Thanks for the link to: web.archive.org/web/20190901011222/http://derrickgilland.com‌​/… . has very good explanation of the issue and How to get aroind it.

[ggorlen]

Information shouldn't be in links. It should be summarized in the answer itself -- the links should be there for support and those who want to dig deeper. The link will disappear someday and render the answer useless. See your answer is in another castle.

[ggorlen]

"For a lot of the simple cases Flask-Sqlalchemy is gonna be totally fine" -- which simple cases? What's "gonna be totally fine", exactly? "Flask-SqlAlchemy is defo a good thing." -- why? This post raises more questions than it answers, and it doesn't clarify what Flask-SqlAlchemy offers relative to SqlAlchemy.