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
The semantic design of the old syntax is not easy to understand and is not user-friendly.
The newly introduced syntax has strong scalability and flexibility to support (multiple) catalog, multiple object type and multiple DBs Backup/Restore.
Expansion of ON clause:
We introduce the key word (TABLE(S)/VIEW(S)/MATERIALIZED VIEW(S)/FUNCTION(S)) to identify different type of Backup/Restore object and use ALL to represent all objects of a certain type which is much more clear the before.
Allow to specify database explicitly and separated from snapshot name: Backup: User can specify database after DATABASE key word or before snapshot name as before.
Restore:
If user does not specify dbname at all (both before snapshot name or after DATABASE keyword) without ON clause, it will create database with the same name in snapshot file and restore all data into it.
If specify dbName after DATABASE keyword, no dbName can be specified before snapshot name.
The dbName after DATABASE keyword must exactly match in snapshot file. DATABASE <db_name> [AS <db_alias>] means that restore the database named by db_name in snapshot to the database named by db_alias in current cluster. If AS is missing, restore to the database with the same name.
The text was updated successfully, but these errors were encountered:
Why we need a new syntax for Backup/Restore
New syntax design for Backup/Restore
The behavioral changes in Backup/Restore syntax
Expansion of
ON
clause:We introduce the key word
(TABLE(S)/VIEW(S)/MATERIALIZED VIEW(S)/FUNCTION(S))
to identify different type of Backup/Restore object and useALL
to represent all objects of a certain type which is much more clear the before.Allow to specify database explicitly and separated from snapshot name:
Backup:
User can specify database after DATABASE key word or before snapshot name as before.Restore:
DATABASE
keyword) withoutON
clause, it will create database with the same name in snapshot file and restore all data into it.DATABASE
keyword, no dbName can be specified before snapshot name.DATABASE
keyword must exactly match in snapshot file.DATABASE <db_name> [AS <db_alias>]
means that restore the database named by db_name in snapshot to the database named by db_alias in current cluster. IfAS
is missing, restore to the database with the same name.The text was updated successfully, but these errors were encountered: