[GH-ISSUE #8065] [Bug] Duplicating Databases Not Creating New Databases #3529

New issue

Open

opened 2026-03-23 21:31:01 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 21:31:01 +00:00

Owner

Originally created by @CurtDagon on GitHub (Jun 15, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8065

Bug Description

Duplicating databases does not make new databases but keeps the same database’s linked. Simply put when you duplicate a “Page” that has a “Grid” then change anything on it those changes will also change the “Grid” that you just duplicated from. Current work around is deleting all databases and having to make new ones from scratch. As there is no current way to change the default template if you have complex or a large amount of items you are wasting so much time having to rebuild everything.

How to Reproduce

Make a "Page" then make a "Grids”, “Board”, and/or “Calendar” change the Title and make some sort of change inside the database. After that duplicate the "Page" with the database and its name will say "Copy" but the databases are still linked to the original.

Expected Behavior

When duplicating the "Page" with the database when the "Copy" is added to the "Page" the databases also get a "Copy" and they are no longer linked to the original database and are now a new database.

Operating System

Windows and Linux

AppFlowy Version(s)

0.9.3

Screenshots

Additional Context

No response

Originally created by @CurtDagon on GitHub (Jun 15, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8065 ### Bug Description Duplicating databases does not make new databases but keeps the same database’s linked. Simply put when you duplicate a “Page” that has a “Grid” then change anything on it those changes will also change the “Grid” that you just duplicated from. Current work around is deleting all databases and having to make new ones from scratch. As there is no current way to change the default template if you have complex or a large amount of items you are wasting so much time having to rebuild everything. ### How to Reproduce Make a "Page" then make a "Grids”, “Board”, and/or “Calendar” change the Title and make some sort of change inside the database. After that duplicate the "Page" with the database and its name will say "Copy" but the databases are still linked to the original. ### Expected Behavior When duplicating the "Page" with the database when the "Copy" is added to the "Page" the databases also get a "Copy" and they are no longer linked to the original database and are now a new database. ### Operating System Windows and Linux ### AppFlowy Version(s) 0.9.3 ### Screenshots ![Image](https://github.com/user-attachments/assets/2a0b9dda-055b-49b4-9f6a-da5303b1aad6) ![Image](https://github.com/user-attachments/assets/3a134dfe-69ea-452c-8873-a0702abcaf01) ![Image](https://github.com/user-attachments/assets/dce20844-01e1-405d-8b29-bd591f59d894) ![Image](https://github.com/user-attachments/assets/bd602488-527c-47b5-8427-ff55537e5b12) ![Image](https://github.com/user-attachments/assets/211a3f30-c241-46c1-afde-7fbf7ad16efc) ### Additional Context _No response_

mirror added the

labels

2026-03-23 21:31:01 +00:00

mirror commented

2026-03-23 21:31:02 +00:00

Author

Owner

@khorshuheng commented on GitHub (Jun 16, 2025):

That is by design - a database referenced in a page is just a reference, rather than the actual database instance. There are use cases where this would be useful, for example, when several pages need to refer to the same database.

If you duplicate the database directly, instead of database referenced within a page, a full copy will be created instead, which can then be referenced separately.

Could it be that, for your use case, what you actually need, is a proper user defined template system (eg. template database, page), rather than changing the currently duplicate feature?

@khorshuheng commented on GitHub (Jun 16, 2025): That is by design - a database referenced in a page is just a reference, rather than the actual database instance. There are use cases where this would be useful, for example, when several pages need to refer to the same database. If you duplicate the database directly, instead of database referenced within a page, a full copy will be created instead, which can then be referenced separately. Could it be that, for your use case, what you actually need, is a proper user defined template system (eg. template database, page), rather than changing the currently duplicate feature?

mirror referenced this issue

2026-03-23 22:20:09 +00:00

[PR #3529] [MERGED] fix: unable to parse html text which contains <mark> tag #5754