Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

🔖 Enhancement description

I would like to have a button to empty a table on the console, on the Settings tab, either on its own section or under the Delete table section. This could be a new command on the SDK too. This will reset the sequence number too.

🎤 Pitch

It would be use it on development phase only, and it's a short-hand to delete and re-create the table with the same structure. Also, it would be shorter than listing all records and deleting them one by one.
I know I could run tablesDB.deleteRows with no queries, but have to use the SDK.

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

You must be logged in to vote

Replies: 1 comment

Comment options

This would actually be a very useful developer-experience improvement, especially during rapid iteration in development and testing environments.

Right now, clearing a table often means either:

  • deleting rows manually
  • writing a temporary SDK/script call
  • dropping and recreating the table
  • running direct database commands externally

For development workflows, that creates unnecessary friction for something that is conceptually a very common operation.

A dedicated “Truncate table” action in the Console would make a lot of sense, particularly if it:

  • removes all rows efficiently
  • resets auto-increment/sequence values
  • preserves schema/indexes/permissions
  • avoids requiring external scripts or SDK usage

Something like this under the Settings section would probably fit naturally:

Danger Zone

[ Truncate Table ]
Removes all rows and resets sequences.
Table structure, indexes, and permissions remain unchanged.

A few safety mechanisms would probably also be important:

  • confirmation modal requiring table name input
  • environment warnings for production projects
  • optional “reset sequences” checkbox
  • audit logging
  • permission restrictions
  • soft-disable in production environments

From an API/SDK perspective, a dedicated operation could also be cleaner than relying on deleteRows() with empty filters, because truncation is semantically different from row-by-row deletion and usually much faster at the database level.

For larger datasets especially, true truncation can provide:

  • significantly faster execution
  • lower transaction overhead
  • reduced lock contention
  • sequence reset support

This feels like one of those small features that ends up saving developers a surprising amount of time during testing and iterative schema development.

Related references:

Definitely seems like a reasonable and practical console enhancement.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
💡
Ideas
Labels
product / databases Fixes and upgrades for the Appwrite Database. product / console Console, UI and UX issues
2 participants
Converted from issue

This discussion was converted from issue #11406 on March 10, 2026 13:02.

Morty Proxy This is a proxified and sanitized view of the page, visit original site.