Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump django-sql-explorer[assistant,uploads] from 5.2b1 to 5.3b1 #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 1, 2024

Bumps django-sql-explorer[assistant,uploads] from 5.2b1 to 5.3b1.

Release notes

Sourced from django-sql-explorer[assistant,uploads]'s releases.

5.3b1 (2024-08-29)

  • #664: Improvements to the AI SQL Assistant:

    • Table Annotations: Write persistent table annotations with descriptive information that will get injected into the prompt for the assistant. For example, if a table is commonly joined to another table through a non-obvious foreign key, you can tell the assistant about it in plain english, as an annotation to that table. Every time that table is deemed 'relevant' to an assistant request, that annotation will be included alongside the schema and sample data.
    • Few-Shot Examples: Using the small checkbox on the bottom-right of any saved queries, you can designate certain queries as 'few shot examples". When making an assistant request, any designated few-shot examples that reference the same tables as your assistant request will get included as 'reference sql' in the prompt for the LLM.
    • Autocomplete / multiselect when selecting tables info to send to the SQL Assistant. Much easier and more keyboard focused.
    • Relevant tables are added client-side visually, in real time, based on what's in the SQL editor and/or any tables mentioned in the assistant request. The dependency on sql_metadata is therefore removed, as server-side SQL parsing is no longer necessary.
    • Ability to view Assistant request/response history.
    • Improved system prompt that emphasizes the particular SQL dialect being used.
    • Addresses issue #657.
  • #660: Userspace connection migration.

    • This should be an invisible change, but represents a significant refactor of how connections function. Instead of a weird blend of DatabaseConnection models and underlying Django models (which were the original Explorer connections), this migrates all connections to DatabaseConnection models and implements proper foreign keys to them on the Query and QueryLog models. A data migration creates new DatabaseConnection models based on the configured settings.EXPLORER_CONNECTIONS. Going forward, admins can create new Django-backed DatabaseConnection models by registering the connection in EXPLORER_CONNECTIONS, and then creating a DatabaseConnection model using the Django admin or the user-facing /connections/new/ form, and entering the Django DB alias and setting the connection type to "Django Connection".
    • The Query.connection and QueryLog.connection fields are deprecated and will be removed in a future release. They are kept around in this release in case there is an unforeseen issue with the migration. Preserving the fields for now ensures there is no data loss in the event that a rollback to an earlier version is required.
  • Fixed a bug when validating connections to uploaded files. Also added basic locking when downloading files from S3.

  • Keyboard shortcut for formatting the SQL in the editor.

    • Cmd+Shift+F (Windows: Ctrl+Shift+F)
    • The format button has been moved tobe a small icon towards the bottom-right of the SQL editor.

5.2.0 (2024-08-19)

  • #651: Improvements to upload file abilities:

    • Ability to append an upload to a previously uploaded file/sqlite DB as a new table
    • Good cache busting and detection of file changes on uploads
    • Significant documentation improvements to uploads and connections
    • Separate the upload UI from the 'add connection' UI, as they are materially different
    • Ability to refresh a connection's schema and data (if it's an upload) from the connections list view
  • #659: Search all queries, even if the header is collapsed. Addresses issue #464 (partially) and #658 (fully).

  • #662: Refactored dockerfile to use non-root directories. Addresses issue #661.

  • Fix a small bug with bar chart generation, when values are null

Changelog

Sourced from django-sql-explorer[assistant,uploads]'s changelog.

========== Change Log

This document records all notable changes to SQL Explorer <https://github.com/explorerhq/sql-explorer>. This project adheres to Semantic Versioning <https://semver.org/>.

5.3.0 (beta)_ (2024-08-29)

  • [#664](https://github.com/explorerhq/sql-explorer/issues/664)_: Improvements to the AI SQL Assistant:

    • Table Annotations: Write persistent table annotations with descriptive information that will get injected into the prompt for the assistant. For example, if a table is commonly joined to another table through a non-obvious foreign key, you can tell the assistant about it in plain english, as an annotation to that table. Every time that table is deemed 'relevant' to an assistant request, that annotation will be included alongside the schema and sample data.
    • Few-Shot Examples: Using the small checkbox on the bottom-right of any saved queries, you can designate certain queries as 'few shot examples". When making an assistant request, any designated few-shot examples that reference the same tables as your assistant request will get included as 'reference sql' in the prompt for the LLM.
    • Autocomplete / multiselect when selecting tables info to send to the SQL Assistant. Much easier and more keyboard focused.
    • Relevant tables are added client-side visually, in real time, based on what's in the SQL editor and/or any tables mentioned in the assistant request. The dependency on sql_metadata is therefore removed, as server-side SQL parsing is no longer necessary.
    • Ability to view Assistant request/response history.
    • Improved system prompt that emphasizes the particular SQL dialect being used.
    • Addresses issue #657.
  • [#660](https://github.com/explorerhq/sql-explorer/issues/660)_: Userspace connection migration.

    • This should be an invisible change, but represents a significant refactor of how connections function. Instead of a weird blend of DatabaseConnection models and underlying Django models (which were the original Explorer connections), this migrates all connections to DatabaseConnection models and implements proper foreign keys to them on the Query and QueryLog models. A data migration creates new DatabaseConnection models based on the configured settings.EXPLORER_CONNECTIONS. Going forward, admins can create new Django-backed DatabaseConnection models by registering the connection in EXPLORER_CONNECTIONS, and then creating a DatabaseConnection model using the Django admin or the user-facing /connections/new/ form, and entering the Django DB alias and setting the connection type to "Django Connection".
    • The Query.connection and QueryLog.connection fields are deprecated and will be removed in a future release. They are kept around in this release in case there is an unforeseen issue with the migration. Preserving the fields for now ensures there is no data loss in the event that a rollback to an earlier version is required.
  • Fixed a bug when validating connections to uploaded files. Also added basic locking when downloading files from S3.

  • Keyboard shortcut for formatting the SQL in the editor.

    • Cmd+Shift+F (Windows: Ctrl+Shift+F)
    • The format button has been moved tobe a small icon towards the bottom-right of the SQL editor.

5.2.0_ (2024-08-19)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [django-sql-explorer[assistant,uploads]](https://github.com/explorerhq/sql-explorer) from 5.2b1 to 5.3b1.
- [Release notes](https://github.com/explorerhq/sql-explorer/releases)
- [Changelog](https://github.com/explorerhq/sql-explorer/blob/master/HISTORY.rst)
- [Commits](https://github.com/explorerhq/sql-explorer/commits)

---
updated-dependencies:
- dependency-name: django-sql-explorer[assistant,uploads]
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants