Flask-sqlalchemy

Latest version: v3.1.1

Safety actively analyzes 629004 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 6

2.4.2

-------------

Released 2020-05-25

- Fix bad pagination when records are de-duped. :pr:`812`

2.4.1

-------------

Released 2019-09-24

- Fix ``AttributeError`` when using multiple binds with polymorphic models. :pr:`651`

2.4.0

-------------

Released 2019-04-24

- Drop support for Python 2.6 and 3.3. :pr:`687`
- Address SQLAlchemy 1.3 deprecations. :pr:`684`
- Make engine configuration more flexible. Added the ``engine_options`` parameter and
``SQLALCHEMY_ENGINE_OPTIONS`` config. Deprecated the individual engine option config
keys ``SQLALCHEMY_NATIVE_UNICODE``, ``SQLALCHEMY_POOL_SIZE``,
``SQLALCHEMY_POOL_TIMEOUT``, ``SQLALCHEMY_POOL_RECYCLE``, and
``SQLALCHEMY_MAX_OVERFLOW``. :pr:`684`
- ``get_or_404()`` and ``first_or_404()`` now accept a ``description`` parameter to
control the 404 message. :issue:`636`
- Use ``time.perf_counter`` for Python 3 on Windows. :issue:`638`
- Add an example of Flask's tutorial project, Flaskr, adapted for Flask-SQLAlchemy.
:pr:`720`

2.3.2

-------------

Released 2017-10-11

- Don't mask the parent table for single-table inheritance models. :pr:`561`

2.3.1

-------------

Released 2017-10-05

- If a model has a table name that matches an existing table in the metadata, use that
table. Fixes a regression where reflected tables were not picked up by models.
:issue:`551`
- Raise the correct error when a model has a table name but no primary key. :pr:`556`
- Fix ``repr`` on models that don't have an identity because they have not been
flushed yet. :issue:`555`
- Allow specifying a ``max_per_page`` limit for pagination, to avoid users specifying
high values in the request args. :pr:`542`
- For ``paginate`` with ``error_out=False``, the minimum value for ``page`` is 1 and
``per_page`` is 0. :issue:`558`

2.3.0

-------------

Released 2017-09-28

- Multiple bugs with ``__tablename__`` generation are fixed. Names will be generated
for models that define a primary key, but not for single-table inheritance
subclasses. Names will not override a ``declared_attr``. ``PrimaryKeyConstraint`` is
detected. :pr:`541`
- Passing an existing ``declarative_base()`` as ``model_class`` to
``SQLAlchemy.__init__`` will use this as the base class instead of creating one.
This allows customizing the metaclass used to construct the base. :issue:`546`
- The undocumented ``DeclarativeMeta`` internals that the extension uses for binds and
table name generation have been refactored to work as mixins. Documentation is added
about how to create a custom metaclass that does not do table name generation.
:issue:`546`
- Model and metaclass code has been moved to a new ``models`` module.
``_BoundDeclarativeMeta`` is renamed to ``DefaultMeta``; the old name will be
removed in 3.0. :issue:`546`
- Models have a default ``repr`` that shows the model name and primary key. :pr:`530`
- Fixed a bug where using ``init_app`` would cause connectors to always use the
``current_app`` rather than the app they were created for. This caused issues when
multiple apps were registered with the extension. :pr:`547`

Page 3 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.