automatic import of python-django-db-viewsopeneuler20.03

3 files changed, 511 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..ff272ab 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/django-db-views-0.1.5.tar.gz
diff --git a/python-django-db-views.spec b/python-django-db-views.spec
new file mode 100644
index 0000000..570cb1e
--- /dev/null
+++ b/python-django-db-views.spec
@@ -0,0 +1,509 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-django-db-views
+Version:	0.1.5
+Release:	1
+Summary:	Handle database views. Allow to create migrations for database views. View migrations using django code. They can be reversed. Changes in model view definition are detected automatically. Support almost all options as regular makemigrations command
+License:	MIT
+URL:		https://github.com/BezBartek/django-db-views
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/11/9e/4c23b18d0bf7297742025d6b38ec3fd6fc9d4a2a468c9a6beb740d19a675/django-db-views-0.1.5.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-Django
+Requires:	python3-six
+
+%description
+# django-db-views
+|  |  |                                                                                                    |
+|--------------------|---------------------|----------------------------------------------------------------------------------------------------|
+| :memo: | **License** | [![License](https://img.shields.io/:license-mit-blue.svg)](http://doge.mit-license.org)            |
+| :package: | **PyPi** | [![PyPi](https://badge.fury.io/py/django-db-views.svg)](https://pypi.org/project/django-db-views/) |
+| <img src="https://cdn.iconscout.com/icon/free/png-256/django-1-282754.png" width="22px" height="22px" align="center" /> | **Django Versions** | 2.2 to 4.0                                                                                         |
+| <img src="http://www.iconarchive.com/download/i73027/cornmanthe3rd/plex/Other-python.ico" width="22px" height="22px" align="center" /> | **Python Versions** | 3.6 to 3.10                                                                                        |
+
+
+### How to install?
+  - `pip install django-db-views`
+
+### What we offer
+ - Database views
+ - Materialized views
+ - views schema migrations 
+ - indexing for materialized views (future)
+ - database table function (future)
+
+### How to use?
+   - add `django_db_views` to `INSTALLED_APPS`
+   - use `makeviewmigrations` command to create migrations for view models
+
+
+### How to create view in your database?
+
+- To create your view use DBView class, remember to set view definition attribute.
+
+
+   ```python
+    from django.db import models
+    from django_db_views.db_view import DBView
+    
+    
+    class VirtualCard(models.Model):
+        ...
+    
+    
+    class Balance(DBView):
+
+        virtual_card = models.ForeignKey(
+            VirtualCard,  # VirtualCard is a regular Django model. 
+            on_delete=models.DO_NOTHING, related_name='virtual_cards'
+        )
+        total_discount = models.DecimalField(max_digits=12, decimal_places=2)
+        total_returns = models.DecimalField(max_digits=12, decimal_places=2)
+        balance = models.DecimalField(max_digits=12, decimal_places=2)
+        
+        view_definition = """
+            SELECT
+                row_number() over () as id,  # Django requires column called id
+                virtual_card.id as virtual_card_id,
+                sum(...) as total_discount,
+            ...
+        """
+    
+        class Meta:
+            managed = False  # Managed must be set to False!
+            db_table = 'virtual_card_balance'
+   ```
+
+
+- The view definition can be: **str/dict** or a callable which returns **str/dict**. 
+
+   Callable view definition examples:
+
+   ```python
+    from django_db_views.db_view import DBViewl
+  
+    class ExampleView(DBView):
+        @staticmethod
+        def view_definition():
+            return str(SomeModel.objects.all().query)
+        # OR
+        view_definition = lambda: str(SomeModel.objects.all().query)
+        class Meta:
+            managed = False 
+            db_table = 'example_view'
+   ```
+
+   using callable allow you to write view definition using ORM.
+
+- Ensure that you include `managed = False` in the DBView model's Meta class to prevent Django creating it's own migration.
+
+### How view migrations work? 
+   - DBView working as regular django model. You can use it in any query. 
+   - It's using Django code, view-migrations looks like regular migrations. 
+   - It relies on `db_table` names. 
+   - `makeviewmigrations` command finds previous migration for view.
+      - if there is no such migration then script create a new migration
+      - if previous migration exists but no change in `view_definition` is detected nothing is done
+      - if previous migration exists, then script will use previous `view_definition` for backward operation, and creates new migration.
+      - when run it will check if the current default engine definined in django.settings is the same engine the view was defined with
+
+
+### Multidatabase support
+Yoy can define view_definition as
+a dict for multiple engine types.
+
+If you do not pass in an engine and have a str or callable the
+engine will be defaulted to the default database defined in django.
+
+It respects --database flag in the migrate command,
+So you are able to define a specific view definitions for specific databases using the engine key.
+If the key do not match your current database, view migration will be skipped.
+
+Also, feature becomes useful if you use a different engine for local / dev / staging / production.
+
+Example dict view definition:
+
+```python
+view_definition = {
+    "django.db.backends.sqlite3": """
+        SELECT
+            row_number() over () as id,
+            q.id as question_id,
+            count(*) as total_choices
+        FROM question q
+        JOIN choice c on c.question_id = q.id
+        GROUP BY q.id
+    """,
+    "django.db.backends.postgresql": """
+        SELECT
+            row_number() over () as id,
+            q.id as question_id,
+            count(*) as total_choices
+        FROM question q
+        JOIN choice c on c.question_id = q.id
+        GROUP BY q.id
+    """,
+}
+```
+
+### Materialized Views
+
+Just inherit from `DBMaterializedView` instead of regular `DBView`
+
+Materialzied View provide an extra class method to refresh view called `refresh`
+
+
+### Notes
+_Please use the newest version. version 0.1.0 has backward
+incompatibility which is solved in version 0.1.1 and higher._
+
+
+
+
+%package -n python3-django-db-views
+Summary:	Handle database views. Allow to create migrations for database views. View migrations using django code. They can be reversed. Changes in model view definition are detected automatically. Support almost all options as regular makemigrations command
+Provides:	python-django-db-views
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-django-db-views
+# django-db-views
+|  |  |                                                                                                    |
+|--------------------|---------------------|----------------------------------------------------------------------------------------------------|
+| :memo: | **License** | [![License](https://img.shields.io/:license-mit-blue.svg)](http://doge.mit-license.org)            |
+| :package: | **PyPi** | [![PyPi](https://badge.fury.io/py/django-db-views.svg)](https://pypi.org/project/django-db-views/) |
+| <img src="https://cdn.iconscout.com/icon/free/png-256/django-1-282754.png" width="22px" height="22px" align="center" /> | **Django Versions** | 2.2 to 4.0                                                                                         |
+| <img src="http://www.iconarchive.com/download/i73027/cornmanthe3rd/plex/Other-python.ico" width="22px" height="22px" align="center" /> | **Python Versions** | 3.6 to 3.10                                                                                        |
+
+
+### How to install?
+  - `pip install django-db-views`
+
+### What we offer
+ - Database views
+ - Materialized views
+ - views schema migrations 
+ - indexing for materialized views (future)
+ - database table function (future)
+
+### How to use?
+   - add `django_db_views` to `INSTALLED_APPS`
+   - use `makeviewmigrations` command to create migrations for view models
+
+
+### How to create view in your database?
+
+- To create your view use DBView class, remember to set view definition attribute.
+
+
+   ```python
+    from django.db import models
+    from django_db_views.db_view import DBView
+    
+    
+    class VirtualCard(models.Model):
+        ...
+    
+    
+    class Balance(DBView):
+
+        virtual_card = models.ForeignKey(
+            VirtualCard,  # VirtualCard is a regular Django model. 
+            on_delete=models.DO_NOTHING, related_name='virtual_cards'
+        )
+        total_discount = models.DecimalField(max_digits=12, decimal_places=2)
+        total_returns = models.DecimalField(max_digits=12, decimal_places=2)
+        balance = models.DecimalField(max_digits=12, decimal_places=2)
+        
+        view_definition = """
+            SELECT
+                row_number() over () as id,  # Django requires column called id
+                virtual_card.id as virtual_card_id,
+                sum(...) as total_discount,
+            ...
+        """
+    
+        class Meta:
+            managed = False  # Managed must be set to False!
+            db_table = 'virtual_card_balance'
+   ```
+
+
+- The view definition can be: **str/dict** or a callable which returns **str/dict**. 
+
+   Callable view definition examples:
+
+   ```python
+    from django_db_views.db_view import DBViewl
+  
+    class ExampleView(DBView):
+        @staticmethod
+        def view_definition():
+            return str(SomeModel.objects.all().query)
+        # OR
+        view_definition = lambda: str(SomeModel.objects.all().query)
+        class Meta:
+            managed = False 
+            db_table = 'example_view'
+   ```
+
+   using callable allow you to write view definition using ORM.
+
+- Ensure that you include `managed = False` in the DBView model's Meta class to prevent Django creating it's own migration.
+
+### How view migrations work? 
+   - DBView working as regular django model. You can use it in any query. 
+   - It's using Django code, view-migrations looks like regular migrations. 
+   - It relies on `db_table` names. 
+   - `makeviewmigrations` command finds previous migration for view.
+      - if there is no such migration then script create a new migration
+      - if previous migration exists but no change in `view_definition` is detected nothing is done
+      - if previous migration exists, then script will use previous `view_definition` for backward operation, and creates new migration.
+      - when run it will check if the current default engine definined in django.settings is the same engine the view was defined with
+
+
+### Multidatabase support
+Yoy can define view_definition as
+a dict for multiple engine types.
+
+If you do not pass in an engine and have a str or callable the
+engine will be defaulted to the default database defined in django.
+
+It respects --database flag in the migrate command,
+So you are able to define a specific view definitions for specific databases using the engine key.
+If the key do not match your current database, view migration will be skipped.
+
+Also, feature becomes useful if you use a different engine for local / dev / staging / production.
+
+Example dict view definition:
+
+```python
+view_definition = {
+    "django.db.backends.sqlite3": """
+        SELECT
+            row_number() over () as id,
+            q.id as question_id,
+            count(*) as total_choices
+        FROM question q
+        JOIN choice c on c.question_id = q.id
+        GROUP BY q.id
+    """,
+    "django.db.backends.postgresql": """
+        SELECT
+            row_number() over () as id,
+            q.id as question_id,
+            count(*) as total_choices
+        FROM question q
+        JOIN choice c on c.question_id = q.id
+        GROUP BY q.id
+    """,
+}
+```
+
+### Materialized Views
+
+Just inherit from `DBMaterializedView` instead of regular `DBView`
+
+Materialzied View provide an extra class method to refresh view called `refresh`
+
+
+### Notes
+_Please use the newest version. version 0.1.0 has backward
+incompatibility which is solved in version 0.1.1 and higher._
+
+
+
+
+%package help
+Summary:	Development documents and examples for django-db-views
+Provides:	python3-django-db-views-doc
+%description help
+# django-db-views
+|  |  |                                                                                                    |
+|--------------------|---------------------|----------------------------------------------------------------------------------------------------|
+| :memo: | **License** | [![License](https://img.shields.io/:license-mit-blue.svg)](http://doge.mit-license.org)            |
+| :package: | **PyPi** | [![PyPi](https://badge.fury.io/py/django-db-views.svg)](https://pypi.org/project/django-db-views/) |
+| <img src="https://cdn.iconscout.com/icon/free/png-256/django-1-282754.png" width="22px" height="22px" align="center" /> | **Django Versions** | 2.2 to 4.0                                                                                         |
+| <img src="http://www.iconarchive.com/download/i73027/cornmanthe3rd/plex/Other-python.ico" width="22px" height="22px" align="center" /> | **Python Versions** | 3.6 to 3.10                                                                                        |
+
+
+### How to install?
+  - `pip install django-db-views`
+
+### What we offer
+ - Database views
+ - Materialized views
+ - views schema migrations 
+ - indexing for materialized views (future)
+ - database table function (future)
+
+### How to use?
+   - add `django_db_views` to `INSTALLED_APPS`
+   - use `makeviewmigrations` command to create migrations for view models
+
+
+### How to create view in your database?
+
+- To create your view use DBView class, remember to set view definition attribute.
+
+
+   ```python
+    from django.db import models
+    from django_db_views.db_view import DBView
+    
+    
+    class VirtualCard(models.Model):
+        ...
+    
+    
+    class Balance(DBView):
+
+        virtual_card = models.ForeignKey(
+            VirtualCard,  # VirtualCard is a regular Django model. 
+            on_delete=models.DO_NOTHING, related_name='virtual_cards'
+        )
+        total_discount = models.DecimalField(max_digits=12, decimal_places=2)
+        total_returns = models.DecimalField(max_digits=12, decimal_places=2)
+        balance = models.DecimalField(max_digits=12, decimal_places=2)
+        
+        view_definition = """
+            SELECT
+                row_number() over () as id,  # Django requires column called id
+                virtual_card.id as virtual_card_id,
+                sum(...) as total_discount,
+            ...
+        """
+    
+        class Meta:
+            managed = False  # Managed must be set to False!
+            db_table = 'virtual_card_balance'
+   ```
+
+
+- The view definition can be: **str/dict** or a callable which returns **str/dict**. 
+
+   Callable view definition examples:
+
+   ```python
+    from django_db_views.db_view import DBViewl
+  
+    class ExampleView(DBView):
+        @staticmethod
+        def view_definition():
+            return str(SomeModel.objects.all().query)
+        # OR
+        view_definition = lambda: str(SomeModel.objects.all().query)
+        class Meta:
+            managed = False 
+            db_table = 'example_view'
+   ```
+
+   using callable allow you to write view definition using ORM.
+
+- Ensure that you include `managed = False` in the DBView model's Meta class to prevent Django creating it's own migration.
+
+### How view migrations work? 
+   - DBView working as regular django model. You can use it in any query. 
+   - It's using Django code, view-migrations looks like regular migrations. 
+   - It relies on `db_table` names. 
+   - `makeviewmigrations` command finds previous migration for view.
+      - if there is no such migration then script create a new migration
+      - if previous migration exists but no change in `view_definition` is detected nothing is done
+      - if previous migration exists, then script will use previous `view_definition` for backward operation, and creates new migration.
+      - when run it will check if the current default engine definined in django.settings is the same engine the view was defined with
+
+
+### Multidatabase support
+Yoy can define view_definition as
+a dict for multiple engine types.
+
+If you do not pass in an engine and have a str or callable the
+engine will be defaulted to the default database defined in django.
+
+It respects --database flag in the migrate command,
+So you are able to define a specific view definitions for specific databases using the engine key.
+If the key do not match your current database, view migration will be skipped.
+
+Also, feature becomes useful if you use a different engine for local / dev / staging / production.
+
+Example dict view definition:
+
+```python
+view_definition = {
+    "django.db.backends.sqlite3": """
+        SELECT
+            row_number() over () as id,
+            q.id as question_id,
+            count(*) as total_choices
+        FROM question q
+        JOIN choice c on c.question_id = q.id
+        GROUP BY q.id
+    """,
+    "django.db.backends.postgresql": """
+        SELECT
+            row_number() over () as id,
+            q.id as question_id,
+            count(*) as total_choices
+        FROM question q
+        JOIN choice c on c.question_id = q.id
+        GROUP BY q.id
+    """,
+}
+```
+
+### Materialized Views
+
+Just inherit from `DBMaterializedView` instead of regular `DBView`
+
+Materialzied View provide an extra class method to refresh view called `refresh`
+
+
+### Notes
+_Please use the newest version. version 0.1.0 has backward
+incompatibility which is solved in version 0.1.1 and higher._
+
+
+
+
+%prep
+%autosetup -n django-db-views-0.1.5
+
+%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-db-views -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.1.5-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..3e98fa0
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+758792e63eea05792774d80b58d4e8cb  django-db-views-0.1.5.tar.gz