jupyter-duckdb 1.2.100__tar.gz → 1.4.106__tar.gz

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.2
+Metadata-Version: 2.4
 Name: jupyter-duckdb
-Version: 1.2.100
+Version: 1.4.106
 Summary: a basic wrapper kernel for DuckDB
 Home-page: https://github.com/erictroebs/jupyter-duckdb
 Author: Eric Tröbs
@@ -12,9 +12,9 @@ Classifier: Operating System :: OS Independent
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 Requires-Dist: jupyter
-Requires-Dist: graphviz==0.20.3
+Requires-Dist: graphviz==0.21
 Requires-Dist: checkmarkandcross
-Requires-Dist: duckdb==1.2.1
+Requires-Dist: duckdb==1.4.1
 Dynamic: author
 Dynamic: author-email
 Dynamic: classifier
@@ -45,6 +45,7 @@ There are some magic commands that make teaching easier with this kernel.
     - [Ship Tests With Your Notebook](#ship-tests-with-your-notebooks)
     - [Relational Algebra](#relational-algebra)
     - [Domain Calculus](#domain-calculus)
+    - [Automated Parser Selection](#automated-parser-selection)
 
 ## Setup
 
@@ -118,23 +119,24 @@ another DuckDB file or a file with SQL statements. In the first case the
 included tables will be copied to the new database, while in the second case the
 SQL statements are just executed. We find this feature very useful to work in a
 temporary copy of the data and therefore be able to restart at any time. The
-last optional parameter `WITH_TESTS` is described in
-detail [below](#ship-tests-with-your-notebooks).
+optional parameter `NAME` may be used to name a connection and reference it
+later by using the magic command `USE`.
 
 ```
 %CREATE data.duckdb OF my_statements.sql
 ```
 
 `LOAD` on the other hand loads an existing database and returns an error if it
-does not exist. (That is why `OF` cannot be used with `LOAD`! `WITH_TESTS` on
-the other hand is available also with this magic command.)
+does not exist. (That is why `OF` cannot be used with `LOAD`! `NAME` on the
+other hand is available also with this magic command.)
 
 ```
 %LOAD data.duckdb
 ```
 
-Only one database can be open at any time. If a new database is created or
-loaded, the current one is closed first and saved to disk if necessary.
+Multiple databases can be open at any time. If a new database with the same
+name is created or loaded, the current one is closed first and saved to disk
+if necessary.
 
 Please note that `:memory:` is also a valid file path for DuckDB. The data is
 then stored exclusively in the main memory. In combination with `CREATE`
@@ -213,10 +215,10 @@ FROM bar
 
 ### Ship Tests With Your Notebooks
 
-Simple tests can be loaded together with the database with the help of
-the `WITH_TESTS` parameter. These tests are stored as a JSON file. Each test is
-assigned a unique name, a result set and whether the test should check the order
-of the result. A very simple test file looks like the following JSON object:
+Simple tests can be loaded from json files with the help of magic command
+`LOAD_TESTS`. These tests are stored as a JSON file. Each test is assigned a
+unique name, a result set and whether the test should check the order of the
+result. A very simple test file looks like the following JSON object:
 
 ```json
 {
@@ -280,6 +282,8 @@ The supported operations are:
 The optional flag `ANALYZE` can be used to add an execution diagram to the
 output.
 
+You can also add comments to queries using `--` or `/* */`, just like in SQL.
+
 The Dockerfile also installs the Jupyter Lab plugin
 [jupyter-ra-extension](https://pypi.org/project/jupyter-ra-extension/). It adds
 the symbols mentioned above and some other supported symbols to the toolbar for
@@ -303,4 +307,3 @@ executed cells.
 If the magic command `%AUTO_PARSER` is added to a cell, a parser is
 automatically selected. If `%GUESS_PARSER` is executed, the parser is
 automatically selected for all subsequent cells.
-

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/README.md

@@ -17,6 +17,7 @@ There are some magic commands that make teaching easier with this kernel.
     - [Ship Tests With Your Notebook](#ship-tests-with-your-notebooks)
     - [Relational Algebra](#relational-algebra)
     - [Domain Calculus](#domain-calculus)
+    - [Automated Parser Selection](#automated-parser-selection)
 
 ## Setup
 
@@ -90,23 +91,24 @@ another DuckDB file or a file with SQL statements. In the first case the
 included tables will be copied to the new database, while in the second case the
 SQL statements are just executed. We find this feature very useful to work in a
 temporary copy of the data and therefore be able to restart at any time. The
-last optional parameter `WITH_TESTS` is described in
-detail [below](#ship-tests-with-your-notebooks).
+optional parameter `NAME` may be used to name a connection and reference it
+later by using the magic command `USE`.
 
 ```
 %CREATE data.duckdb OF my_statements.sql
 ```
 
 `LOAD` on the other hand loads an existing database and returns an error if it
-does not exist. (That is why `OF` cannot be used with `LOAD`! `WITH_TESTS` on
-the other hand is available also with this magic command.)
+does not exist. (That is why `OF` cannot be used with `LOAD`! `NAME` on the
+other hand is available also with this magic command.)
 
 ```
 %LOAD data.duckdb
 ```
 
-Only one database can be open at any time. If a new database is created or
-loaded, the current one is closed first and saved to disk if necessary.
+Multiple databases can be open at any time. If a new database with the same
+name is created or loaded, the current one is closed first and saved to disk
+if necessary.
 
 Please note that `:memory:` is also a valid file path for DuckDB. The data is
 then stored exclusively in the main memory. In combination with `CREATE`
@@ -185,10 +187,10 @@ FROM bar
 
 ### Ship Tests With Your Notebooks
 
-Simple tests can be loaded together with the database with the help of
-the `WITH_TESTS` parameter. These tests are stored as a JSON file. Each test is
-assigned a unique name, a result set and whether the test should check the order
-of the result. A very simple test file looks like the following JSON object:
+Simple tests can be loaded from json files with the help of magic command
+`LOAD_TESTS`. These tests are stored as a JSON file. Each test is assigned a
+unique name, a result set and whether the test should check the order of the
+result. A very simple test file looks like the following JSON object:
 
 ```json
 {
@@ -252,6 +254,8 @@ The supported operations are:
 The optional flag `ANALYZE` can be used to add an execution diagram to the
 output.
 
+You can also add comments to queries using `--` or `/* */`, just like in SQL.
+
 The Dockerfile also installs the Jupyter Lab plugin
 [jupyter-ra-extension](https://pypi.org/project/jupyter-ra-extension/). It adds
 the symbols mentioned above and some other supported symbols to the toolbar for
@@ -275,4 +279,3 @@ executed cells.
 If the magic command `%AUTO_PARSER` is added to a cell, a parser is
 automatically selected. If `%GUESS_PARSER` is executed, the parser is
 automatically selected for all subsequent cells.
-

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/setup.py

@@ -1,12 +1,12 @@
 import os
 
 # configuration
-PACKAGE_VERSION = '1.2.100'
-DUCKDB_VERSION = '1.2.1'
+PACKAGE_VERSION = '1.4.106'
+DUCKDB_VERSION = '1.4.1'
 
 DEPENDENCIES = [
     'jupyter',
-    'graphviz==0.20.3',
+    'graphviz==0.21',
     'checkmarkandcross'
 ]
 
@@ -46,7 +46,9 @@ if __name__ == '__main__':
         include_package_data=True,
         package_data={
             'duckdb_kernel': [
-                'kernel.json'
+                'kernel.json',
+                'visualization/lib/*.css',
+                'visualization/lib/*.js',
             ]
         }
     )

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/src/duckdb_kernel/db/Connection.py

@@ -10,6 +10,9 @@ class Connection:
     def close(self):
         pass
 
+    def copy(self) -> 'Connection':
+        raise NotImplementedError
+
     @staticmethod
     def plain_explain() -> bool:
         return False

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/src/duckdb_kernel/db/implementation/duckdb/Connection.py

@@ -15,6 +15,9 @@ class Connection(Base):
     def close(self):
         self.con.close()
 
+    def copy(self) -> 'Connection':
+        return Connection(self.path)
+
     @staticmethod
     def plain_explain() -> bool:
         return True

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/src/duckdb_kernel/db/implementation/postgres/Connection.py

@@ -19,6 +19,7 @@ class Connection(Base):
         self.host: str = host
         self.port: int = port
         self.username: Optional[str] = username
+        self.password: Optional[str] = password
 
         options = {
             'host': host,
@@ -43,6 +44,9 @@ class Connection(Base):
     def close(self):
         self.con.close()
 
+    def copy(self) -> 'Connection':
+        return Connection(self.host, self.port, self.username, self.password, self.database_name)
+
     def __str__(self) -> str:
         user = f'{self.username}@' if self.username is not None else ''
         return f'PostgreSQL: {user}{self.host}:{self.port}/{self.database_name}'
@@ -63,7 +67,10 @@ class Connection(Base):
                 rows = cursor.fetchall()
             except psycopg.ProgrammingError as e:
                 text = str(e)
-                if text == "the last operation didn't produce a result":
+                if text.startswith((
+                        "the last operation didn't produce a result",
+                        "the last operation didn't produce records"
+                )):
                     raise EmptyResultError()
                 else:
                     raise e

{jupyter_duckdb-1.2.100 → jupyter_duckdb-1.4.106}/src/duckdb_kernel/db/implementation/sqlite/Connection.py

@@ -16,6 +16,9 @@ class Connection(Base):
     def close(self):
         self.con.close()
 
+    def copy(self) -> 'Connection':
+        return Connection(self.path)
+
     @staticmethod
     def multiple_statements_per_query() -> bool:
         return False