`where` not respected after upgrading to 0.4.0
See original GitHub issueIts seems upgrading has broken all my tables as they pull false positives. It seems that something in the where
parameter is not being respected.
Typical Example:
table Topic, Message
from #message
where contains(projects, this.file.link)
sort file.mtime asc
Where my page would have:
Projects:: [[linked page]]
It seems that tables that just refer to this.file.link
also pull many false positives, so it may not just be contains
either.
Great work. Good to see it progressing forward.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
npm-update does NOT follow SemVer · Issue #3579 · npm/cli
This command will update all the packages listed to the latest version (specified by the tag config), respecting the semver constraints of ...
Read more >Upgrade Guides | Nomad
The log_file configuration option was not being fully respected, as the generated filename would include a timestamp. After upgrade, the active log file ......
Read more >Upgrading — Vagga 0.8.1 documentation - Read the Docs
The /etc/resolv.conf and /etc/hosts files are now cleaned after container build and mounted over by system files. This may slightly tweak behavior when...
Read more >Upgrading the Postgres Operator Release
This topic provides steps to upgrade the Postgres operator currently deployed in your Kubernetes cluster to a new Postgres operator version.
Read more >Upgrading the Operator - GitLab Docs
To address this, identify a valid version from that release's available chart versions. For example: when upgrading from Operator 0.4.0 to 0.4.1 ,...
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
Also had to fix link comparisons. See if this issue is solved in release 0.4.1, which has just come out.
I can confirm, that the issues I saw are now solved. Swift solution! Awesome! Similar to the comments above, I could deal with not using Dataview, but who wants to do that!