Version 3.7.3

Compatibility

1. Fix compatibility with psycpg3 by @LorenzoProd

Version 3.7.2

Requirements

1. MInimized requirements, so psycopg2 or psycopg2-binary can be used (removed it from requirements at all)

CI

1. Added django 5.0

Version 3.7.1

Bug fixes

1. Fixed issue #92 in pdnf_clause, if initial data was empty.

Compatibility

1. Fixed django 4.0+ compatibility

Version 3.7.0

Enhancements

1. Set functions now can have different value types supported_field_classes:

• Field classes (any child classes are accepted too)
• Field class python import paths (any child classes are accepted too)
• Filed class names (behavior before this version, now inheritance here)

Version 3.6.0

Features

1. Added ability to use BulkValue() in set function in form of django expression

Version 3.5.1

Bug fixes

1. Fixed issue #84 : functions used as default field value are now handled correctly

Requirements

1. Replaced psycop2-binary with psycopg2 in requirements files

Testing

1. Added django 4.0 to GitHub Actions

Version 3.5.0

Features

1. Added ability to use django expressions as set functions

Version 3.4.5

Tests

1. Fixed tests by issue #70

Bug fixes

1. Fixed issue #71 :now if set functions which don't require a value get it from user's input it is ignored

Features

1. Optimized batching mechanics
2. Minor refactoring

Version 3.4.4

Bug fixes

1. Thanks to @dhendry, user set_functions are now prior to standard NowSetFunction when field has auto_now or auto_now_add options.

Compatibility

1. Fixed python 3.10 compatibility (@dhendry)

Testing

1. Removed python 3.5
2. Added python 3.10 and PostgreSQL 13

Version 3.4.3

Bug fixes

1. Fixed django 3.2 compatibility