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.

Sign up for GitHub

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

Jump to bottom

use limit_zero macro instead of limit 0 #437

Merged
merged 4 commits into from
Nov 9, 2021
Merged

use limit_zero macro instead of limit 0 #437

merged 4 commits into from
Nov 9, 2021

Conversation

dataders
Copy link
Contributor

@dataders dataders commented Nov 8, 2021 •
edited
Loading

This is a:

  • bug fix PR with no breaking changes — please ensure the base branch is master
  • new functionality — please ensure the base branch is the latest dev/ branch
  • a breaking change — please ensure the base branch is the latest dev/ branch

Description & motivation

This test cannot be used by databases that don't support limit zero

Checklist

  • I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
    • BigQuery
    • Postgres
    • Redshift
    • Snowflake
  • I have "dispatched" any new macro(s) so non-core adapters can also use them (e.g. the star() source)
  • I have updated the README.md (if applicable)
  • I have added tests & descriptions to my models (and macros if applicable)
  • I have added an entry to CHANGELOG.md

joellabes and others added 2 commits October 28, 2021 12:00
@joellabes @TimoKruth @fivetran-joemarkiewicz
Utils 0.7.4b1 (dbt-labs#433)
cd4c5e2 
* Update require-dbt-version to be 1.0

* Fix SQL 42000 on Exasol (dbt-labs#420)

" SQL-Error [42000]: syntax error, unexpected '*' "
If you specify the * in the unioned with their respectiv names <name>.* you do not receive the SQL Error posted above. This should not inflict any further problems since it is redundant for most DBs.

* Minor readme link fixes (dbt-labs#431)

* minor readme link fixes

* changelog addition

Co-authored-by: Joel Labes <[email protected]>

* 0.7.4 changelog (dbt-labs#432)

* Update CHANGELOG.md

* Note branch name change

Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>
@dataders
standard convention
147404e
@dataders dataders mentioned this pull request Nov 8, 2021
Merged
12 tasks
joellabes
joellabes requested changes Nov 9, 2021
View reviewed changes
Copy link
Contributor

@joellabes joellabes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CI test is failing with

Database Error in test test_slugify (tests/jinja_helpers/test_slugify.sql)
  syntax error at or near "object"
  LINE 9:     select 1 <dbt.clients.jinja.MacroGenerator object at 0x7...
                                                         ^
  compiled SQL at target/run/dbt_utils_integration_tests/tests/jinja_helpers/test_slugify.sql
Encountered an error:
FailFast Error in test test_slugify (tests/jinja_helpers/test_slugify.sql)
  Failing early due to test failure or runtime error

However a test like assert_pretty_time_is_string is passing and looks almost identical. The only thing that jumps out is this one doesn't alias select 1. It shouldn't need to - the code you've written works for me when I test it in dbt Cloud - but let's give it a whirl just in case.

@joellabes
Update integration_tests/tests/jinja_helpers/test_slugify.sql
d7c6e9b 
Taking the liberty of committing on your behalf so that the CI job starts again
joellabes
joellabes requested changes Nov 9, 2021
View reviewed changes
Copy link
Contributor

@joellabes joellabes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a macro! that's why there was an error 🎉

@dataders
Copy link
Contributor Author

dataders commented Nov 9, 2021

thanks @joellabes this should be ready now IMHO

@dataders dataders requested a review from joellabes November 9, 2021 18:15
@joellabes joellabes changed the base branch from main to next/patch November 9, 2021 20:44
joellabes
joellabes approved these changes Nov 9, 2021
View reviewed changes
Copy link
Contributor

@joellabes joellabes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks as always for your contribution!

@joellabes joellabes merged commit 38839fd into dbt-labs:next/patch Nov 9, 2021
@joellabes joellabes mentioned this pull request Nov 9, 2021
Closed
12 tasks
joellabes added a commit that referenced this pull request Nov 9, 2021
@joellabes
Add col_name alias to else state too (#437)
c2f228f
joellabes added a commit that referenced this pull request Nov 11, 2021
@joellabes @TimoKruth
@fivetran-joemarkiewicz @dataders @sean-rose
dbt 0.7.4 release (#441)
b42e6f9 
* Update require-dbt-version to be 1.0

* Fix SQL 42000 on Exasol (#420)

" SQL-Error [42000]: syntax error, unexpected '*' "
If you specify the * in the unioned with their respectiv names <name>.* you do not receive the SQL Error posted above. This should not inflict any further problems since it is redundant for most DBs.

* Minor readme link fixes (#431)

* minor readme link fixes

* changelog addition

Co-authored-by: Joel Labes <[email protected]>

* 0.7.4 changelog (#432)

* Update CHANGELOG.md

* Note branch name change

* use `limit_zero` macro instead of `limit 0` (#437)

* Utils 0.7.4b1  (#433)

* Update require-dbt-version to be 1.0

* Fix SQL 42000 on Exasol (#420)

" SQL-Error [42000]: syntax error, unexpected '*' "
If you specify the * in the unioned with their respectiv names <name>.* you do not receive the SQL Error posted above. This should not inflict any further problems since it is redundant for most DBs.

* Minor readme link fixes (#431)

* minor readme link fixes

* changelog addition

Co-authored-by: Joel Labes <[email protected]>

* 0.7.4 changelog (#432)

* Update CHANGELOG.md

* Note branch name change

Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>

* standard convention

* Update integration_tests/tests/jinja_helpers/test_slugify.sql

Taking the liberty of committing on your behalf so that the CI job starts again

* Change limit_zero to be a macro

Co-authored-by: Joel Labes <[email protected]>
Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>

* Add col_name alias to else state too (#437)

* Remove extra semicolon in `insert_by_period` materialization (#439)

* Remove extra semicolon in `insert_by_period` materialization.

`create_table_as()` generates a SQL statement that already ends with a semicolon, so the extra semicolon after a `create_table_as()` call in the `insert_by_period` materialization ends up being an empty SQL statement, and at least when using Snowflake this causes the dbt run to fail with a "cannot unpack non-iterable NoneType object" error.

* Update changelog for PR 439.

* Use the relation object passed into get_column_values, instead of making our own (#440)

* Use the relation object passed into get_column_values, instead of making our own

* Rename variables in get column value test to be clearer

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>
Co-authored-by: Anders <[email protected]>
Co-authored-by: Sean Rose <[email protected]>
joellabes added a commit that referenced this pull request Dec 2, 2021
@joellabes @TimoKruth
@fivetran-joemarkiewicz @dataders @sean-rose
dbt v1 compat (#453)
baf4053 
* dbt 0.7.4 release (#441)

* Update require-dbt-version to be 1.0

* Fix SQL 42000 on Exasol (#420)

" SQL-Error [42000]: syntax error, unexpected '*' "
If you specify the * in the unioned with their respectiv names <name>.* you do not receive the SQL Error posted above. This should not inflict any further problems since it is redundant for most DBs.

* Minor readme link fixes (#431)

* minor readme link fixes

* changelog addition

Co-authored-by: Joel Labes <[email protected]>

* 0.7.4 changelog (#432)

* Update CHANGELOG.md

* Note branch name change

* use `limit_zero` macro instead of `limit 0` (#437)

* Utils 0.7.4b1  (#433)

* Update require-dbt-version to be 1.0

* Fix SQL 42000 on Exasol (#420)

" SQL-Error [42000]: syntax error, unexpected '*' "
If you specify the * in the unioned with their respectiv names <name>.* you do not receive the SQL Error posted above. This should not inflict any further problems since it is redundant for most DBs.

* Minor readme link fixes (#431)

* minor readme link fixes

* changelog addition

Co-authored-by: Joel Labes <[email protected]>

* 0.7.4 changelog (#432)

* Update CHANGELOG.md

* Note branch name change

Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>

* standard convention

* Update integration_tests/tests/jinja_helpers/test_slugify.sql

Taking the liberty of committing on your behalf so that the CI job starts again

* Change limit_zero to be a macro

Co-authored-by: Joel Labes <[email protected]>
Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>

* Add col_name alias to else state too (#437)

* Remove extra semicolon in `insert_by_period` materialization (#439)

* Remove extra semicolon in `insert_by_period` materialization.

`create_table_as()` generates a SQL statement that already ends with a semicolon, so the extra semicolon after a `create_table_as()` call in the `insert_by_period` materialization ends up being an empty SQL statement, and at least when using Snowflake this causes the dbt run to fail with a "cannot unpack non-iterable NoneType object" error.

* Update changelog for PR 439.

* Use the relation object passed into get_column_values, instead of making our own (#440)

* Use the relation object passed into get_column_values, instead of making our own

* Rename variables in get column value test to be clearer

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>
Co-authored-by: Anders <[email protected]>
Co-authored-by: Sean Rose <[email protected]>

* Regression: Correctly handle missing relations in get_column_values (#448)

* Create integration test for a dropped relation

* Update get_column_values.sql

* Swap out adapter call for a good old fashioned drop table

* Add missing curlies

* what person wrote this code :/ (it was me)

* wrap values in quotes

* GOOD

* bigquery compat (they don't like except)

* Backport android url changes from #426 (#452)

* Update CHANGELOG.md

* Change require-dbt-version, update dbt_project.yml for integration tests proj

* Upgrade python version in CI, improve drop relation integration test

* Clarify version pinning

* Drop support for release candidates of 1.0.0

Co-authored-by: Timo Kruth <[email protected]>
Co-authored-by: Joe Markiewicz <[email protected]>
Co-authored-by: Anders <[email protected]>
Co-authored-by: Sean Rose <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@joellabes joellabes joellabes approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dataders @joellabes