openstack/deb-python-sqlalchemy-utils
Code Issues Proposed changes

Bump version

Browse Source
This commit is contained in:
Konsta Vesterinen
2014-05-07 15:10:01 +03:00
parent 134f112697
commit 5b00373f9f
4 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
CHANGES.rst
View File

@@ -4,12 +4,13 @@ Changelog
Here you can see the full list of changes between each SQLAlchemy-Utils release. Here you can see the full list of changes between each SQLAlchemy-Utils release.
0.26.0 (2014-xx-xx) 0.26.0 (2014-05-07)
^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^
- Added get_referencing_foreign_keys - Added get_referencing_foreign_keys
- Added get_tables - Added get_tables
- Added QueryChain - Added QueryChain
- Added dependent_objects
0.25.4 (2014-04-22) 0.25.4 (2014-04-22)

2
setup.py
View File

@@ -44,7 +44,7 @@ for name, requirements in extras_require.items():
setup( setup(
name='SQLAlchemy-Utils', name='SQLAlchemy-Utils',
version='0.25.4', version='0.26.0',
url='https://github.com/kvesteri/sqlalchemy-utils', url='https://github.com/kvesteri/sqlalchemy-utils',
license='BSD', license='BSD',
author='Konsta Vesterinen, Ryan Leckey, Janne Vanhala, Vesa Uimonen', author='Konsta Vesterinen, Ryan Leckey, Janne Vanhala, Vesa Uimonen',

2
sqlalchemy_utils/__init__.py
View File

@@ -64,7 +64,7 @@ from .types import (
) )
__version__ = '0.25.4' __version__ = '0.26.0'
__all__ = ( __all__ = (

9
sqlalchemy_utils/functions/orm.py
View File

@@ -40,13 +40,14 @@ def dependent_objects(obj, foreign_keys=None):
dependent_objects(user).limit(5) dependent_objects(user).limit(5)
The common use case is checking for all dependent objects before deleting
parent object and inform the user if there are dependent objects with The common use case is checking for all restrict dependent objects before
ondelete='RESTRICT' foreign keys. If this kind of checking is not used deleting parent object and inform the user if there are dependent objects
with ondelete='RESTRICT' foreign keys. If this kind of checking is not used
it will lead to nasty IntegrityErrors being raised. it will lead to nasty IntegrityErrors being raised.
In the following example we delete given user if it doesn't have any In the following example we delete given user if it doesn't have any
foreign key restricted dependent_objects. foreign key restricted dependent objects.
:: ::