diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-django-cursor-pagination.spec | 135 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 137 insertions, 0 deletions
@@ -0,0 +1 @@ +/django-cursor-pagination-0.2.1.tar.gz diff --git a/python-django-cursor-pagination.spec b/python-django-cursor-pagination.spec new file mode 100644 index 0000000..e35d048 --- /dev/null +++ b/python-django-cursor-pagination.spec @@ -0,0 +1,135 @@ +%global _empty_manifest_terminate_build 0 +Name: python-django-cursor-pagination +Version: 0.2.1 +Release: 1 +Summary: Cursor based pagination for Django +License: BSD +URL: https://github.com/photocrowd/django-cursor-pagination +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/15/f3/440595f30fe96870ac3f3ebc119782161cef2d6cc747f288740ac0076679/django-cursor-pagination-0.2.1.tar.gz +BuildArch: noarch + + +%description +A cursor based pagination system for Django. Instead of refering to specific +pages by number, we give every item in the queryset a cursor based on its +ordering values. We then ask for subsequent records by asking for records +*after* the cursor of the last item we currently have. Similarly we can ask for +records *before* the cursor of the first item to navigate back through the +list. +This approach has two major advantages over traditional pagination. Firstly, it +ensures that when new data is written into the table, records cannot be moved +onto the next page. Secondly, it is much faster to query against the database +as we are not using very large offset values. +There are some significant drawbacks over "traditional" pagination. The data +must be ordered by some database field(s) which are unique across all records. +A typical use case would be ordering by a creation timestamp and an id. It is +also more difficult to get the range of possible pages for the data. +The inspiration for this project is largely taken from [this +post](http://cra.mr/2011/03/08/building-cursors-for-the-disqus-api) by David +Cramer, and the connection spec for [Relay +GraphQL](https://facebook.github.io/relay/graphql/connections.htm). Much of the +implementation is inspired by [Django rest framework's Cursor +pagination.](https://github.com/tomchristie/django-rest-framework/blob/9b56dda91850a07cfaecbe972e0f586434b965c3/rest_framework/pagination.py#L407-L707). +The main difference between the Disqus approach and the one used here is that +we require the ordering to be totally determinate instead of using offsets. + +%package -n python3-django-cursor-pagination +Summary: Cursor based pagination for Django +Provides: python-django-cursor-pagination +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-django-cursor-pagination +A cursor based pagination system for Django. Instead of refering to specific +pages by number, we give every item in the queryset a cursor based on its +ordering values. We then ask for subsequent records by asking for records +*after* the cursor of the last item we currently have. Similarly we can ask for +records *before* the cursor of the first item to navigate back through the +list. +This approach has two major advantages over traditional pagination. Firstly, it +ensures that when new data is written into the table, records cannot be moved +onto the next page. Secondly, it is much faster to query against the database +as we are not using very large offset values. +There are some significant drawbacks over "traditional" pagination. The data +must be ordered by some database field(s) which are unique across all records. +A typical use case would be ordering by a creation timestamp and an id. It is +also more difficult to get the range of possible pages for the data. +The inspiration for this project is largely taken from [this +post](http://cra.mr/2011/03/08/building-cursors-for-the-disqus-api) by David +Cramer, and the connection spec for [Relay +GraphQL](https://facebook.github.io/relay/graphql/connections.htm). Much of the +implementation is inspired by [Django rest framework's Cursor +pagination.](https://github.com/tomchristie/django-rest-framework/blob/9b56dda91850a07cfaecbe972e0f586434b965c3/rest_framework/pagination.py#L407-L707). +The main difference between the Disqus approach and the one used here is that +we require the ordering to be totally determinate instead of using offsets. + +%package help +Summary: Development documents and examples for django-cursor-pagination +Provides: python3-django-cursor-pagination-doc +%description help +A cursor based pagination system for Django. Instead of refering to specific +pages by number, we give every item in the queryset a cursor based on its +ordering values. We then ask for subsequent records by asking for records +*after* the cursor of the last item we currently have. Similarly we can ask for +records *before* the cursor of the first item to navigate back through the +list. +This approach has two major advantages over traditional pagination. Firstly, it +ensures that when new data is written into the table, records cannot be moved +onto the next page. Secondly, it is much faster to query against the database +as we are not using very large offset values. +There are some significant drawbacks over "traditional" pagination. The data +must be ordered by some database field(s) which are unique across all records. +A typical use case would be ordering by a creation timestamp and an id. It is +also more difficult to get the range of possible pages for the data. +The inspiration for this project is largely taken from [this +post](http://cra.mr/2011/03/08/building-cursors-for-the-disqus-api) by David +Cramer, and the connection spec for [Relay +GraphQL](https://facebook.github.io/relay/graphql/connections.htm). Much of the +implementation is inspired by [Django rest framework's Cursor +pagination.](https://github.com/tomchristie/django-rest-framework/blob/9b56dda91850a07cfaecbe972e0f586434b965c3/rest_framework/pagination.py#L407-L707). +The main difference between the Disqus approach and the one used here is that +we require the ordering to be totally determinate instead of using offsets. + +%prep +%autosetup -n django-cursor-pagination-0.2.1 + +%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-cursor-pagination -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.1-1 +- Package Spec generated @@ -0,0 +1 @@ +e974eeba8e419f02be09cd37fcfeb65c django-cursor-pagination-0.2.1.tar.gz |