Matthew Somerville 86d9b10dc3 Instead of using DjangoJSONEncoder, use base_field's value_to_string. ...

Note this means the serialization of e.g. IntegerRangeField now has
strings for lower and upper, so use to_python when they came back in
(same behaviour as ArrayField, hopefully, from where I also got the
set_attributes_from_name function).

2015-06-06 12:55:04 +01:00

..

array_default_migrations

Refs #22962 -- Made test case use non-conflicting table names

2015-02-13 14:01:54 +01:00

migrations

Fixed #24837 -- field__contained_by=Range

2015-06-04 19:29:59 +01:00

__init__.py

Name PostgreSQL correctly.

2015-05-30 23:10:30 +01:00

fields.py

Fixed #24604 -- Added JSONField to contrib.postgres.

2015-05-30 23:10:30 +01:00

models.py

Fixed #24837 -- field__contained_by=Range

2015-06-04 19:29:59 +01:00

test_aggregates.py

Name PostgreSQL correctly.

2015-05-30 23:10:30 +01:00

test_array.py

Name PostgreSQL correctly.

2015-05-30 23:10:30 +01:00

test_hstore.py

Name PostgreSQL correctly.

2015-05-30 23:10:30 +01:00

test_json.py

Name PostgreSQL correctly.

2015-05-30 23:10:30 +01:00

test_ranges.py

Instead of using DjangoJSONEncoder, use base_field's value_to_string.

2015-06-06 12:55:04 +01:00

test_unaccent.py

Name PostgreSQL correctly.

2015-05-30 23:10:30 +01:00