Feature: RENAME statement for fields, databases and events

[itsezc]

Is your feature request related to a problem?

For the purposes of database migrations in production, it is necessary that fields, events, and even databases among other entities (i.e. namespaces), would need to be renamed.

Describe the solution

Provide RENAME as a Surreal SQL statement

Alternative methods

Copying data across fields / tables to rename them, which feels very much like an anti-pattern

SurrealDB version

surreal 1.0.0-beta.8 for linux on x86_64

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[cameronbraid]

Consider an alternative which may be suitable for a number of use cases which would avoid surreal having to do any data updates when certain 'renames' are needed

Allow aliases to be defined for namespace, database and tables - using tables as an example :

alias table page_views to page_views_x

then whenever interacting with the storage layer resolve the alias page_views into page_views_x

so select * from page_views would end up as select * from page_views_x

then when the alias is changed

alias table page_views to page_views_y

then select * from page_views would end up as select * from page_views_y

A use case for this is when doing CDC import from another database. Say I wanted to restart the CDC connector for table 'page_views' (which already has some corrupted data in it) I would point the new connector to table 'page_views_x' then when the snapshot has completed, I can switch over queries to run from this new table with the alias command.

[itsezc]

Fixed by: #4465 @kearfy

[kearfy]

Renaming resources is not actually aolved yet, leaving it open 😁