Skip to content

Migrate whenever#2

Open
sungchun12 wants to merge 22 commits intoduckdbfrom
migrate-whenever
Open

Migrate whenever#2
sungchun12 wants to merge 22 commits intoduckdbfrom
migrate-whenever

Conversation

@sungchun12
Copy link
Owner

No description provided.

dbeatty10 and others added 22 commits July 22, 2022 10:16
* 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 <kirafuruichi2019@u.northwestern.edu>

* Apply suggestions from code review

Expand the description in the "What's in this repo?" section

Co-authored-by: Kira Furuichi <kirafuruichi2019@u.northwestern.edu>

Co-authored-by: Kira Furuichi <kirafuruichi2019@u.northwestern.edu>
* 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
* dbt Core 1.3 release candidate

* Bump version for duckcli
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants