diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2015-08-17 17:04:33 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2015-08-17 17:12:16 -0400 |
| commit | d14a4b480c3b43885707e4a6e2466589971ff4d5 (patch) | |
| tree | fab9267e749501c7b32c9e6e9f9f8429ef2b5644 /lib/sqlalchemy/dialects/postgresql/array.py | |
| parent | ceeb033054f09db3eccbde3fad1941ec42919a54 (diff) | |
| download | sqlalchemy-d14a4b480c3b43885707e4a6e2466589971ff4d5.tar.gz | |
- merge of ticket_3514 None-handling branch
- Fixes to the ORM and to the postgresql JSON type regarding the
``None`` constant in conjunction with the Postgresql :class:`.JSON` type. When
the :paramref:`.JSON.none_as_null` flag is left at its default
value of ``False``, the ORM will now correctly insert the Json
"'null'" string into the column whenever the value on the ORM
object is set to the value ``None`` or when the value ``None``
is used with :meth:`.Session.bulk_insert_mappings`,
**including** if the column has a default or server default on it. This
makes use of a new type-level flag "evaluates_none" which is implemented
by the JSON type based on the none_as_null flag. fixes #3514
- Added a new constant :attr:`.postgresql.JSON.NULL`, indicating
that the JSON NULL value should be used for a value
regardless of other settings. part of fixes #3514
Diffstat (limited to 'lib/sqlalchemy/dialects/postgresql/array.py')
0 files changed, 0 insertions, 0 deletions