From d0357b44b02324b85af42052487eab13d0b75f81 Mon Sep 17 00:00:00 2001 From: Armin Ronacher Date: Thu, 1 Jul 2010 01:22:46 +0200 Subject: [PATCH] Added links to Flask-WTF and Flask-SQLAlchemy. This fixes #73 --- docs/patterns/sqlalchemy.rst | 16 +++++++++++++++- docs/patterns/wtforms.rst | 9 +++++++++ 2 files changed, 24 insertions(+), 1 deletion(-) diff --git a/docs/patterns/sqlalchemy.rst b/docs/patterns/sqlalchemy.rst index 6a14c8e0..a66627ad 100644 --- a/docs/patterns/sqlalchemy.rst +++ b/docs/patterns/sqlalchemy.rst @@ -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 +`_. + +.. _Flask-SQLAlchemy: http://packages.python.org/Flask-SQLAlchemy/ + + Declarative ----------- diff --git a/docs/patterns/wtforms.rst b/docs/patterns/wtforms.rst index d62c5bd3..8a113cc5 100644 --- a/docs/patterns/wtforms.rst +++ b/docs/patterns/wtforms.rst @@ -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 + `_. + +.. _Flask-WTF: http://packages.python.org/Flask-WTF/ + The Forms ---------