[Feature Request]: Database Views

[tiagosales]

Description

It would be great if we could use database views across different pages, linking to an existing database (table).

Use case

Suppose we want to create a project based on a template and view only tasks assigned to this specific project on the page. I have a tasks database page with a table containing tasks for all my projects. On the project page, I want to see only tasks for that specific project, using the view linked to a tasks database but displaying only the tasks relevant to this project.

Anything else?

In Notion, it would be equivalent to creating a new table on a new page and linking it to an existing database, allowing you to create as many specific views as you want without affect the database itself.

If this feature already exists, please let me know, as I couldn't find a way to use it.

https://www.notion.com/help/data-sources-and-linked-databases

Are you willing to submit a PR?

• Yes I'd like to help by submitting a PR!

[affine-issue-bot[bot]]

Issue Status: 🆕 *Untriaged

*🆕 Untriaged

The team has not yet reviewed the issue. We usually do it within one business day.
Docs: https://github.com/toeverything/AFFiNE/blob/canary/docs/issue-triaging.md

^{_{This is an automatic reply by the bot.}}

[hwangdev97]

Yep, that's exactly the functionality we're aiming for!

But right now, we're mainly focused on squashing bugs, boosting performance, and making the database architecture more stable. We'll start rollin' out these features gradually in future updates.

[ntexier-belenos]

Hi team,

First, thank you for confirming that cross-page database views are on the roadmap!

I have started to explore how to implement such feature that would allow users to select and display any database (table) from any page in the workspace, similar to Notion’s “linked database” feature. However, I’ve run into a technical limitation:

Current technical challenge:

It seems that database blocks are only accessible if their parent page/document is loaded and “ready.”
When iterating over the workspace’s document collection, only the current (loaded) page exposes its blocks. For other pages, the store is not ready, and methods like getBlocksByFlavour('affine:database') return nothing or fail.
There doesn’t seem to be a global index or registry of all databases in the workspace.
Questions:

Is there a recommended way (or a planned API) to access database blocks from other pages, even if those pages are not currently loaded?
Would it make sense to have a “public database” page or a global index of databases that could be referenced from any page, as a workaround or architectural solution?
Are there any best practices or patterns you recommend for this kind of cross-page access, or should we wait for the official feature?
Any advice or pointers would be greatly appreciated.
Thanks for your work and for considering this use case!