1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
|
%global _empty_manifest_terminate_build 0
Name: python-django-pghistory
Version: 2.7.0
Release: 1
Summary: History tracking for Django and Postgres
License: BSD-3-Clause
URL: https://github.com/Opus10/django-pghistory
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/d9/85/d551c0353358902263f126014e3054567dc0a12100bb0ff132ce8f7307b9/django_pghistory-2.7.0.tar.gz
BuildArch: noarch
Requires: python3-django
Requires: python3-importlib_metadata
Requires: python3-django-pgtrigger
%description
Decorate your model with ``pghistory.track``. For example:
import pghistory
@pghistory.track(pghistory.Snapshot())
class TrackedModel(models.Model):
int_field = models.IntegerField()
text_field = models.TextField()
Above we've registered a ``pghistory.Snapshot`` event tracker to ``TrackedModel``.
This event tracker stores every change in a dynamically-created
model that mirrors fields in ``TrackedModel``.
Run ``python manage.py makemigrations`` followed by ``migrate`` and
*voila*, every change to ``TrackedModel`` is now stored. This includes bulk
methods and even changes that happen in raw SQL. For example:
from myapp.models import TrackedModel
# Even though we didn't declare TrackedModelEvent, django-pghistory
# creates it for us in our app
from myapp.models import TrackedModelEvent
m = TrackedModel.objects.create(int_field=1, text_field="hello")
m.int_field = 2
m.save()
print(TrackedModelEvent.objects.values("pgh_obj", "int_field"))
> [{'pgh_obj': 1, 'int_field': 1}, {'pgh_obj': 1, 'int_field': 2}]
Above we printed the ``pgh_obj`` field, which is a special foreign key to the tracked
object. There are a few other special ``pgh_`` fields that we'll discuss later.
``django-pghistory`` can track a subset of fields and conditionally store events
based on specific field transitions. Users can also store free-form context
from the application that's referenced by the event model, all with no additional
database queries. See the next steps below on how to dive deeper and configure it
for your use case.
%package -n python3-django-pghistory
Summary: History tracking for Django and Postgres
Provides: python-django-pghistory
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-django-pghistory
Decorate your model with ``pghistory.track``. For example:
import pghistory
@pghistory.track(pghistory.Snapshot())
class TrackedModel(models.Model):
int_field = models.IntegerField()
text_field = models.TextField()
Above we've registered a ``pghistory.Snapshot`` event tracker to ``TrackedModel``.
This event tracker stores every change in a dynamically-created
model that mirrors fields in ``TrackedModel``.
Run ``python manage.py makemigrations`` followed by ``migrate`` and
*voila*, every change to ``TrackedModel`` is now stored. This includes bulk
methods and even changes that happen in raw SQL. For example:
from myapp.models import TrackedModel
# Even though we didn't declare TrackedModelEvent, django-pghistory
# creates it for us in our app
from myapp.models import TrackedModelEvent
m = TrackedModel.objects.create(int_field=1, text_field="hello")
m.int_field = 2
m.save()
print(TrackedModelEvent.objects.values("pgh_obj", "int_field"))
> [{'pgh_obj': 1, 'int_field': 1}, {'pgh_obj': 1, 'int_field': 2}]
Above we printed the ``pgh_obj`` field, which is a special foreign key to the tracked
object. There are a few other special ``pgh_`` fields that we'll discuss later.
``django-pghistory`` can track a subset of fields and conditionally store events
based on specific field transitions. Users can also store free-form context
from the application that's referenced by the event model, all with no additional
database queries. See the next steps below on how to dive deeper and configure it
for your use case.
%package help
Summary: Development documents and examples for django-pghistory
Provides: python3-django-pghistory-doc
%description help
Decorate your model with ``pghistory.track``. For example:
import pghistory
@pghistory.track(pghistory.Snapshot())
class TrackedModel(models.Model):
int_field = models.IntegerField()
text_field = models.TextField()
Above we've registered a ``pghistory.Snapshot`` event tracker to ``TrackedModel``.
This event tracker stores every change in a dynamically-created
model that mirrors fields in ``TrackedModel``.
Run ``python manage.py makemigrations`` followed by ``migrate`` and
*voila*, every change to ``TrackedModel`` is now stored. This includes bulk
methods and even changes that happen in raw SQL. For example:
from myapp.models import TrackedModel
# Even though we didn't declare TrackedModelEvent, django-pghistory
# creates it for us in our app
from myapp.models import TrackedModelEvent
m = TrackedModel.objects.create(int_field=1, text_field="hello")
m.int_field = 2
m.save()
print(TrackedModelEvent.objects.values("pgh_obj", "int_field"))
> [{'pgh_obj': 1, 'int_field': 1}, {'pgh_obj': 1, 'int_field': 2}]
Above we printed the ``pgh_obj`` field, which is a special foreign key to the tracked
object. There are a few other special ``pgh_`` fields that we'll discuss later.
``django-pghistory`` can track a subset of fields and conditionally store events
based on specific field transitions. Users can also store free-form context
from the application that's referenced by the event model, all with no additional
database queries. See the next steps below on how to dive deeper and configure it
for your use case.
%prep
%autosetup -n django-pghistory-2.7.0
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-django-pghistory -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 2.7.0-1
- Package Spec generated
|
