| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2015-12-01 | [1.9.x] Pulled contrib translations from Transifex | Claude Paroz | |
| 2015-11-25 | [1.9.x] Fixed #25772 -- Corrected __len lookup on ArrayField for empty arrays. | Attila Tovt | |
| Backport of 88fc9e2826044110b7b22577a227f122fe9c1fb5 from master | |||
| 2015-11-14 | [1.9.x] Fixed #25666 -- Fixed the exact lookup of ArrayField. | Dmitry Dygalo | |
| Backport of 263b3d2ba132ea443193dc0b728741317742c8d3 from master | |||
| 2015-10-27 | [1.9.x] Fixed #25597 -- Fixed crash with SplitArrayField and IntegerField on ↵ | Tim Graham | |
| invalid value. Backport of 1f07da3e29c7c3d47968e1c4531dd9bf902575b7 from master | |||
| 2015-10-09 | [1.9.x] Updated translation catalogs | Claude Paroz | |
| 2015-09-21 | Fixed #24629 -- Unified Transform and Expression APIs | Josh Smeaton | |
| 2015-08-07 | Fixed #25233 -- Fixed HStoreField.has_changed() handling of initial values. | Tim Graham | |
| Thanks Simon Charette for review. | |||
| 2015-08-05 | Fixed #25226 -- Set the model attribute on ArrayField's base_field | Ion Scerbatiuc | |
| 2015-08-04 | Fixed #25215 -- Solved reference to forms.HStoreField in declaration of ↵ | Curtis Maloney | |
| HStoreField Correct test which was using the model field in a test form. | |||
| 2015-07-14 | Fixed #24716 -- Deprecated Field._get_val_from_obj() | Thomas Stephenson | |
| The method duplicates the functionality of Field.value_from_object() and has the additional downside of being a privately named public API method. | |||
| 2015-06-15 | Fixed #24894 -- Added contrib.postgres.functions.TransactionNow | Adam Chainz | |
| 2015-06-06 | Instead of using DjangoJSONEncoder, use base_field's value_to_string. | Matthew Somerville | |
| 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-05 | Fixed #24937 -- fix serialization of Date(Time)RangeField. | Matthew Somerville | |
| Use the DjangoJSONEncoder so that datetime and date are encoded appropriately. | |||
| 2015-06-04 | Fixed #24837 -- field__contained_by=Range | Marc Tamlyn | |
| Provide `contained_by` lookups for the equivalent single valued fields related to the range field types. This acts as the opposite direction to rangefield__contains. With thanks to schinckel for the idea and initial tests. | |||
| 2015-05-30 | Fixed #24604 -- Added JSONField to contrib.postgres. | Marc Tamlyn | |
| 2015-05-30 | Add HasAnyKeys lookup for HStoreField. | Marc Tamlyn | |
| 2015-05-25 | Fixed #24841 -- Made BaseRangeField.prepare_value() call base_field's ↵ | Villiers Strauss | |
| prepare_value() | |||
| 2015-05-24 | Fixed #24844 -- Corrected has_changed implementation for HStoreField. | Andrea Grandi | |
| 2015-05-13 | Removed unnecessary arguments in .get method calls | Piotr Jakimiak | |
| 2015-05-13 | Fixed #24751 -- Fixed HStoreField isnull lookup. | Tim Graham | |
| 2015-04-30 | Updated translations from Transifex | Claude Paroz | |
| Updates for languages: Indonesian, Belarusian, Persian, and Dutch. Forward port of cb370f8510 from stable/1.8.x | |||
| 2015-04-18 | Stopped special-casing postgres-specific tests | Claude Paroz | |
| Refs #23879. | |||
| 2015-04-01 | Fetched updated contrib translations from Transifex | Claude Paroz | |
| Forward port of 5483c66f85 from stable/1.8.x | |||
| 2015-03-30 | Fixed #24301 -- Added PostgreSQL-specific aggregate functions | Andriy Sokolovskiy | |
| 2015-03-25 | Renamed Field.rel attribute to remote_field | Anssi Kääriäinen | |
| Field.rel is now deprecated. Rel objects have now also remote_field attribute. This means that self == self.remote_field.remote_field. In addition, made the Rel objects a bit more like Field objects. Still, marked ManyToManyFields as null=True. | |||
| 2015-03-18 | Updated translation catalogs | Claude Paroz | |
| Strings are frozen in anticipation of the Django 1.8 release. Forward port of 1cd2584c980 from stable/1.8.x | |||
| 2015-02-20 | Fixed #24341 -- Added specific error messages to RangeField subclasses | foresmac | |
| 2015-02-20 | Fixed #24373 -- Added run_validators to ArrayField. | Marc Tamlyn | |
| Thanks to DavidMuller for the report. | |||
| 2015-02-06 | Sorted imports with isort; refs #23860. | Tim Graham | |
| 2015-01-22 | Fixed #24170 -- Implemented decompress for BaseRangeField widgets | Ng Zhi An | |
| 2015-01-20 | Fixes #24169 -- More arrayfield specific lookups. | Marc Tamlyn | |
| varchar()[] cannot compare itself to text[] Thanks to joelburton for the patch. | |||
| 2015-01-19 | Fixed header of contrib.postgres translation catalog | Claude Paroz | |
| 2015-01-18 | Added contrib.postgres translation catalog | Claude Paroz | |
| Forward port of 8c8a1a084 from stable/1.8.x. | |||
| 2015-01-16 | Fixed #24092 -- Widened base field support for ArrayField. | Marc Tamlyn | |
| Several issues resolved here, following from a report that a base_field of GenericIpAddressField was failing. We were using get_prep_value instead of get_db_prep_value in ArrayField which was bypassing any extra modifications to the value being made in the base field's get_db_prep_value. Changing this broke datetime support, so the postgres backend has gained the relevant operation methods to send dates/times/datetimes directly to the db backend instead of casting them to strings. Similarly, a new database feature has been added allowing the uuid to be passed directly to the backend, as we do with timedeltas. On the other side, psycopg2 expects an Inet() instance for IP address fields, so we add a value_to_db_ipaddress method to wrap the strings on postgres. We also have to manually add a database adapter to psycopg2, as we do not wish to use the built in adapter which would turn everything into Inet() instances. Thanks to smclenithan for the report. | |||
| 2015-01-10 | Fixed #24001 -- Added range fields for PostgreSQL. | Marc Tamlyn | |
| Added support for PostgreSQL range types to contrib.postgres. - 5 new model fields - 4 new form fields - New validators - Uses psycopg2's range type implementation in python | |||
| 2015-01-10 | Move % addition to lookups, refactor postgres lookups. | Marc Tamlyn | |
| These refactorings making overriding some text based lookup names on other fields (specifically `contains`) much cleaner. It also removes a bunch of duplication in the contrib.postgres lookups. | |||
| 2014-12-21 | Fixed #24034 -- Don't always overwrite deconstruct path. | Jernej Kos | |
| Made deconstruct path overwriting for ArrayField conditional, so it only occurs when the deconstructed field is an instance of ArrayField itself and not a subclass. | |||
| 2014-12-09 | Remove text-mangling of default values. | Marc Tamlyn | |
| 2014-12-08 | Fixed #23968 -- Replaced list comprehension with generators and dict ↵ | Jon Dufresne | |
| comprehension | |||
| 2014-11-28 | Fixed #23423 -- Added unaccent lookup in django.contrib.postgres | Thomas Chaumeny | |
| 2014-11-28 | Fixed #23894 -- Made deconstruct methods favor kwargs over args | Markus Holtermann | |
| 2014-11-22 | Revert "Fixed #23892 -- Made deconstructible classes forwards compatible" | Carl Meyer | |
| This reverts commit f36151ed169813f2873e13ca9de616cfa4095321. Adding kwargs to deconstructed objects does not achieve useful forward-compatibility in general, since additional arguments are silently dropped rather than having their intended effect. In fact, it can make the failure more difficult to diagnose. Thanks Shai Berger for discussion. | |||
| 2014-11-22 | Fixed #23892 -- Made deconstructible classes forwards compatible | Carl Meyer | |
| 2014-11-16 | Renamed qn to compiler | Josh Smeaton | |
| 2014-11-15 | added test and fix to check for default null on ArrayField | Daan Vielen | |
| 2014-11-04 | Added HStoreField. | Marc Tamlyn | |
| Thanks to `django-hstore` for inspiration in some areas, and many people for reviews. | |||
| 2014-10-09 | Fixed #23627 -- Allowed register_lookup to work as a decorator. | Marc Tamlyn | |
| 2014-07-29 | Fixed #22962 -- Default values for ArrayField with migrations. | Marc Tamlyn | |
| Fields normally try to force the default value to a string. As translatable strings are not valid default values for ArrayField, we can remove this behaviour which was causing issues with some migrations. Thanks to @schinckel for the report. | |||
| 2014-07-15 | Fixed #22907 -- Array contains must have same type. | Marc Tamlyn | |
| 2014-06-17 | Fixed #22819 -- Renamed output_type -> output_field in query expression API. | Tim Graham | |
| Thanks jorgecarleitao for the suggestion. | |||
