Problem with assert referenced columns are present in datasource
See original GitHub issue@villebro , I have an issue with #10451
It breaks the following type of jinja-based filters:
{% set min_tracking = filter_values('min_sem_tracking', -9 )[0] %}
{% set max_tracking = filter_values('max_sem_tracking', 2 )[0] %}
SELECT
...
WHERE
sem_tracking > {min_tracking} AND sem_tracking < {max_tracking}
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
I get a SQL Syntax Problem The Error is (Error Code 3780)
General error: 3780 Referencing column 'post_id' and referenced column 'id' in foreign key constraint 'fk_post' are incompatible (1 answer).
Read more >Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
Read more >assertj-examples/TableAssertionExamples.java at main - GitHub
Table table = new Table(dataSource, "members");. // There is assertion to test the column and row size. assertThat(table).hasNumberOfColumns(6);.
Read more >2 Server Error Message Reference - MySQL :: Developer Zone
Message: The foreign server name you are trying to reference does not exist. Data source error: %s. Error number: 1478 ; Symbol: ER_ILLEGAL_HA_CREATE_OPTION ......
Read more >Solving 5 Mysterious Spark Errors | by yhoztak - Medium
This error usually happens when two dataframes, and you apply udf on some columns to transfer, aggregate, rejoining to add as new fields...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to reproduce, thanks @lilila and @bkyryliuk for helping track this down. Working on a fix now.
@lilila is the behavior consistent? There is a problem that causes chart loading errors on
1.0.0rc1
that should be fixed by this PR: #12489