mirror of https://github.com/pallets/flask.git
Added links to Flask-WTF and Flask-SQLAlchemy. This fixes #73
This commit is contained in:
parent
e75322206d
commit
d0357b44b0
|
@ -8,9 +8,23 @@ encouraged to use a package instead of a module for your flask application
|
|||
and drop the models into a separate module (:ref:`larger-applications`).
|
||||
While that is not necessary, it makes a lot of sense.
|
||||
|
||||
There are three very common ways to use SQLAlchemy. I will outline each
|
||||
There are four very common ways to use SQLAlchemy. I will outline each
|
||||
of them here:
|
||||
|
||||
Flask-SQLAlchemy Extension
|
||||
--------------------------
|
||||
|
||||
Because SQLAlchemy is a common database abstraction layer and object
|
||||
relational mapper that requires a little bit of configuration effort,
|
||||
there is a Flask extension that handles that for you. This is recommended
|
||||
if you want to get started quickly.
|
||||
|
||||
You can download `Flask-SQLAlchemy`_ from `PyPI
|
||||
<http://pypi.python.org/pypi/Flask-SQLAlchemy>`_.
|
||||
|
||||
.. _Flask-SQLAlchemy: http://packages.python.org/Flask-SQLAlchemy/
|
||||
|
||||
|
||||
Declarative
|
||||
-----------
|
||||
|
||||
|
|
|
@ -12,6 +12,15 @@ first. I recommend breaking up the application into multiple modules
|
|||
(:ref:`larger-applications`) for that and adding a separate module for the
|
||||
forms.
|
||||
|
||||
.. admonition:: Getting most of WTForms with an Extension
|
||||
|
||||
The `Flask-WTF`_ extension expands on this pattern and adds a few
|
||||
handful little helpers that make working with forms and Flask more
|
||||
fun. You can get it from `PyPI
|
||||
<http://pypi.python.org/pypi/Flask-WTF>`_.
|
||||
|
||||
.. _Flask-WTF: http://packages.python.org/Flask-WTF/
|
||||
|
||||
The Forms
|
||||
---------
|
||||
|
||||
|
|
Loading…
Reference in New Issue