You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In both cases I am stuck right at the beginning. The command anyquery -q "SELECT * FROM notion_database" throws the error "could not request the rows from the plugin. Unexpected EOF". See attachment. It does fetch the right table but does not show the content..
Any idea what I am missing?
Thanks and regards!
The text was updated successfully, but these errors were encountered:
Hi @rungioia,
When Anyquery returns unexpected EOF, it means the plugin has crashed, and it shouldn't be happening.
Which version of Anyquery are you running (run anyquery -v)? If it is different from 0.3.1, please update Anyquery.
Then, update the Notion plugin by running anyquery plugin update notion.
The issue may still be present, but Anyquery will return more information to help me debug the issue.
Hi @julien040,
Thanks! I have updated both Anyquery and the Notion plugin.
I can now fetch the table on my private Notion account, see attachment 1.
I'd like to do the same for work. I am part of a Notion team workspace.
Unfortunately on my work account the version 0.3.1 still has the issue both on a private page and on a shared page (team workspace).
The error message is the same, see attachment 2. The columns displayed match the ones of the table I am interested in but the rows can't be shown.
Any idea what it could be?
Hi,
I've installed the notion plugin and followed the steps in here on both a private page and a shared workspace. https://anyquery.dev/recipes/how-to-run-sql-queries-on-a-notion-database
In both cases I am stuck right at the beginning. The command anyquery -q "SELECT * FROM notion_database" throws the error "could not request the rows from the plugin. Unexpected EOF". See attachment. It does fetch the right table but does not show the content..
Any idea what I am missing?
Thanks and regards!

The text was updated successfully, but these errors were encountered: