Save The Change takes this:
>>> lancelot = Knight.objects.get(name="Sir Lancelot")
>>> lancelot.favorite_color = "Blue"
>>> lancelot.save()And does this:
UPDATE "roundtable_knight"
SET "favorite_color" = 'Blue'Instead of this:
UPDATE "roundtable_knight"
SET "name" = 'Sir Lancelot',
"from" = 'Camelot',
"quest" = 'To seek the Holy Grail.',
"favorite_color" = 'Blue',
"epithet" = 'The brave',
"actor" = 'John Cleese',
"full_name" = 'John Marwood Cleese',
"height" = '6''11"',
"birth_date" = '1939-10-27',
"birth_union" = 'UK',
"birth_country" = 'England',
"birth_county" = 'Somerset',
"birth_town" = 'Weston-Super-Mare',
"facial_hair" = 'mustache',
"graduated" = true,
"university" = 'Cambridge University',
"degree" = 'LL.B.',Installation
Install Save The Change just like everything else:
$ pip install django-save-the-changeDocumentation
Full documentation is available at ReadTheDocs.
History
1.1.0 (05/16/2014)
Add proper support for ForeignKeys (thanks to Brandon Konkle and Brian Wilson).
Add update_together field to model Meta, via UpdateTogetherModel.
1.0.0 (09/08/2013)
Initial release.
1 maintainer
Metadata
1 maintainer
Release files for django-save-the-change 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-save-the-change-1.1.0.tar.gz | 5.6 kB | Without provenance | Details |
Release files / django-save-the-change-1.1.0.tar.gz
| Download URL | django-save-the-change-1.1.0.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7fd5332fa121a73b256909d32d4bc1848dc1349877388f818b6a18e5fd924ad7
|
|
BLAKE2b-256 checksum How to use checksums |
ee4c10a34da09eba0f29a675af4ea8be87bfacac717b3f725349ed5af05fd4cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-save-the-change 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
