[Bug]: Relations columns showing content of own DB instead of linked DB
See original GitHub issueContact Details
No response
What happened?
DB type: tag column type: relation target: “media” DB

result: the suggestion show all the entries of the current DB (weekly notes) instead of the target DB
Additionally, another bug is present: if the DB uses a dataview query, the suggestions are empty:

What platform were you using?
Desktop
Version of the plugin
2.8.1
Relevant log output
No errors in the console
Are you using the latest version of the plugin in your Obsidian vault?
- I have verified that I am on the latest version
Are you check if there is a similar issue?
- I have verified that there are not similar issues
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Create and manage relationships in Power BI Desktop
Power BI Desktop looks at column names in the tables you're querying to determine if there are any potential relationships.
Read more >sql - Postgresql tables exists, but getting "relation does not ...
The query you have shown can't work. WHERE table_name="my_table"; is invalid because "my_table" references a column name and there is no such column...
Read more >Solved: Can´t create a relationship between two columns be...
Hi. In Desktop Power BI, I have made a report, with 3 excel files, and want to make a link between these excel...
Read more >Chapter 3. Data, Tables, and Database Design
Data, Tables, and Database Design GIGO—Garbage In, Garbage Out—means that all ... Right-click anywhere in the Relationships window and select Show Table.
Read more >Relations & rollups – Notion Help Center
Contents. What is a database relation? Example use cases; Create a relation; Two-way relations; View and remove related pages; Display options for relations...
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 Free
Top 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
I can confirm this behaviour if I set the source of the database to tag. If the source of the database is set to current folder the functionality works as expected. I did not test any other sources, so maybe the bug is not exclusive to tag
could you share more details?
Looks fine for me since 2.9.0