forked from dbt-labs/jaffle_shop_duckdb
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Migrate whenever #2
Open
sungchun12
wants to merge
22
commits into
duckdb
Choose a base branch
from
migrate-whenever
base: duckdb
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Mach speed instructions for variety of shells * Consistent python reference for pip upgrade * Apply suggestions from code review Move the "Prerequisites: Python >= 3.5" directly underneath the "Running this project" H2 Co-authored-by: Kira Furuichi <[email protected]> * Apply suggestions from code review Expand the description in the "What's in this repo?" section Co-authored-by: Kira Furuichi <[email protected]> Co-authored-by: Kira Furuichi <[email protected]>
* initial commit * remove ref to dockerized MS SQL container * consolidate Dockerfile * drop compose file * move to it's own dir * simplify * egg= be nuts * more settings * add more extensions * drop commented-out settings * add additional packages * move dbt power user to recommended * flatten structure? * add sqlfluff * formatting json * drop pylance preference * move to recommended * experiment * no longer needed bc env is set * auto start terminal with dbt build * add PR dbt version back for CI tests * oopsie type * add docs * Update README.md * Update README.md
add YAML autocomplete via JSONSchema
* dbt Core 1.3 release candidate * Bump version for duckcli
Docker instructions
* add fun colors! * bronze, silver, gold layers
* Move to an .in file for pip-tools * Instructions to pin/lock requirements * Pinned/locked requirements for dbt 1.5.0
We wanted to move this project to the latest dbt-core version to ensure it operates on a version of dbt-core that has addressed the security issue (CVE-2024-22195) with Jinja2. By association we also had to upgrade the version of dbt-duckdb being used. Tangentially we also upgraded the version of sqlfluff.
…ncies The `requirements.txt` was regenerated by first deleting the existing `requirements.txt` and then running `$ pip-compile`.
…exclude-Jinja2-3.1.2-new Upgrade Jinja2 dependency version specification to address CVE-2024-22195
This reverts commit f51b08d.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.