Skip to content

Database governance built for humans and agents — controlling changes and access across every major database.

fix: i18n (#19200)

ecmadaof44c7388640b
diff --git a/frontend/src/components/Plan/components/IssueReviewView/Sidebar/ChecksSection.vue b/frontend/src/components/Plan/components/IssueReviewView/Sidebar/ChecksSection.vue
index 32294616d1..e8307c0dd4 100644
--- a/frontend/src/components/Plan/components/IssueReviewView/Sidebar/ChecksSection.vue
+++ b/frontend/src/components/Plan/components/IssueReviewView/Sidebar/ChecksSection.vue
@@ -13,7 +13,7 @@
<template #icon>
<PlayIcon class="w-4 h-4" />
</template>
- {{ $t("common.run") }}
+ {{ $t("plan.run") }}
</NButton>
</div>
<div class="flex items-center gap-2">
diff --git a/frontend/src/components/Plan/components/PlanCheckSection/PlanCheckSection.vue b/frontend/src/components/Plan/components/PlanCheckSection/PlanCheckSection.vue
index 30d9213226..f0473312af 100644
--- a/frontend/src/components/Plan/components/PlanCheckSection/PlanCheckSection.vue
+++ b/frontend/src/components/Plan/components/PlanCheckSection/PlanCheckSection.vue
@@ -25,7 +25,7 @@
<template #icon>
<PlayIcon class="w-4 h-4" />
</template>
- {{ $t("common.run") }}
+ {{ $t("plan.run") }}
</NButton>
</div>
diff --git a/frontend/src/components/Plan/components/SQLCheckV1Section/SQLCheckV1Section.vue b/frontend/src/components/Plan/components/SQLCheckV1Section/SQLCheckV1Section.vue
index 8c94815892..ef6027a933 100644
--- a/frontend/src/components/Plan/components/SQLCheckV1Section/SQLCheckV1Section.vue
+++ b/frontend/src/components/Plan/components/SQLCheckV1Section/SQLCheckV1Section.vue
@@ -14,7 +14,7 @@
<template #icon>
<PlayIcon class="w-4 h-4" />
</template>
- {{ $t("common.run") }}
+ {{ $t("plan.run") }}
</NButton>
</div>
diff --git a/frontend/src/locales/en-US.json b/frontend/src/locales/en-US.json
index f7c50df322..2b43edfd55 100644
--- a/frontend/src/locales/en-US.json
+++ b/frontend/src/locales/en-US.json
@@ -441,7 +441,7 @@
},
"im": {
"add-im-integration": "Add IM Integration",
- "add-another-im": "Add Anothr IM"
+ "add-another-im": "Add Another IM"
},
"profile": {
"email": "Email",
@@ -1142,6 +1142,7 @@
"overview": {
"no-checks": "No checks"
},
+ "run": "Run check",
"navigator": {
"changes": "Changes",
"checks": "Checks",
@@ -1519,8 +1520,7 @@
"create": "Create Environment",
"reorder": "Reorder Environments",
"successfully-updated-environment": "Successfully updated environment '{name}'.",
- "production-environment": "Production environment",
- "statement-execution": {}
+ "production-environment": "Production environment"
},
"quick-start": {
"self": "Quickstart",
diff --git a/frontend/src/locales/es-ES.json b/frontend/src/locales/es-ES.json
index 4a186e22d0..2161a333e0 100644
--- a/frontend/src/locales/es-ES.json
+++ b/frontend/src/locales/es-ES.json
@@ -209,7 +209,7 @@
"clear-filters": "Limpiar filtros",
"license": "Licencia",
"view-details": "Ver detalles",
- "untitled": "Intitulado",
+ "untitled": "Sin título",
"add-permissions": "Agregar permisos",
"missing-required-permission": "Faltan permisos requeridos {permissions}",
"missing-required-permission-for-resource": "Faltan permisos requeridos para el recurso {resource}",
@@ -221,7 +221,7 @@
"resource-not-found": "Recurso no encontrado",
"continue-anyway": "De todas maneras, continúe",
"permissions": "Permisos",
- "leave-without-saving": "¿Salir sin ahorrar?",
+ "leave-without-saving": "¿Salir sin guardar?",
"configure-now": "Configurar ahora",
"connection": "Conexión",
"resource": "Recurso",
@@ -239,8 +239,8 @@
"title": "Título",
"text-wrap": "Ajuste de texto",
"catalog": "Catálogo",
- "removed": "Remoto",
- "submit": "Entregar",
+ "removed": "Eliminado",
+ "submit": "Enviar",
"draft": "Borrador",
"import": "Importar",
"hard-delete": {
@@ -382,7 +382,7 @@
"database-sync": "Sincronización de bases de datos",
"transaction": "Transacción",
"prior-backup": "Copia de seguridad previa",
- "retry": "Rever",
+ "retry": "Reintentar",
"compute-diff": "Calcular diferencia",
"release-file-execute": "Archivo de lanzamiento"
},
@@ -756,7 +756,7 @@
"self": "Tiempo máximo de consulta",
"description": "El tiempo máximo permitido para la ejecución de una consulta."
},
- "seconds": "Artículos de segunda clase",
+ "seconds": "Segundos",
"project-scope": "proyecto",
"environment-scope": "ambiente"
},
@@ -1015,7 +1015,7 @@
"description": "Filtrar por etiqueta de problema"
},
"table": {
- "title": "Mesa",
+ "title": "Tabla",
"description": "Ingrese el valor y luego presione Enter"
},
"label": {
@@ -1057,7 +1057,7 @@
"reopened": "reabierto",
"action-n-issues": "{action} {n} incidencia | {action} {n} incidencias",
"closed": "cerrado",
- "close": "Cerca"
+ "close": "Cerrar"
},
"approval-flow": {
"self": "Flujo de aprobación"
@@ -1142,13 +1142,14 @@
"overview": {
"no-checks": "Sin controles"
},
+ "run": "Ejecutar verificación",
"navigator": {
"changes": "Cambios",
- "checks": "Cheques",
+ "checks": "Verificaciones",
"statement-empty": "La declaración está vacía"
},
"checks": {
- "self": "Cheques",
+ "self": "Verificaciones",
"no-results-match-filters": "No hay resultados que coincidan con sus filtros",
"no-check-results": "Sin resultados de verificación"
},
@@ -1221,7 +1222,7 @@
"bypass-stage-requirements": "Advertencias de bypass",
"task-execution-errors": "Errores de ejecución de tareas",
"stage": {
- "self": "Escenario | Escenarios",
+ "self": "Etapa | Etapas",
"run-stage": "Ejecutar tareas",
"confirm-create": "¿Está seguro de que desea crear tareas para esta etapa?"
},
@@ -1282,7 +1283,7 @@
"n-databases-had-sync-errors": "{0} base(s) de datos tuvieron errores de sincronización",
"failed-to-sync-schema": "No se pudo sincronizar el esquema",
"successfully-synced-schema": "Esquema sincronizado correctamente",
- "procedures": "Trámites",
+ "procedures": "Procedimientos",
"partitions": "Particiones",
"packages": "Paquetes",
"sequences": "Secuencias",
@@ -1319,7 +1320,7 @@
"sync-new": "Sincronizar únicamente bases de datos nuevas",
"sync-all-tip": "La sincronización de la base de datos es asincrónica y puede tardar entre unos segundos y minutos."
},
- "no-environment": "Esta instancia no ha sido ligada al medio ambiente.",
+ "no-environment": "Esta instancia no ha sido ligada al entorno.",
"selected-n-instances": "{n} instancia seleccionada | {n} instancias seleccionadas",
"users": "Usuarios",
"successfully-restored-instance": "Se restauró exitosamente la instancia '{0}'.",
@@ -1439,7 +1440,7 @@
"vault-auth-type": {
"self": "Tipo de autenticación",
"token": {
- "self": "Simbólico",
+ "self": "Token",
"tips": "Un token raíz sin TTL."
},
"approle": {
@@ -1498,7 +1499,7 @@
"advanced-search": {
"scope": {
"host": {
- "title": "Anfitrión",
+ "title": "Host",
"description": "Filtrar por host de instancia. Introduce el valor y pulsa Intro."
},
"port": {
@@ -1519,8 +1520,7 @@
"create": "Crear entorno",
"reorder": "Reordenar entornos",
"successfully-updated-environment": "entorno '{name}' actualizado exitosamente.",
- "production-environment": "Entorno de producción",
- "statement-execution": {}
+ "production-environment": "Entorno de producción"
},
"quick-start": {
"self": "Inicio rápido",
@@ -1705,7 +1705,7 @@
"foreign-key": {
"reference": "Referencia"
},
- "checks": "Cheques",
+ "checks": "Verificaciones",
"engine-not-supported-for-backup": "No se admite la copia de seguridad previa para: {databases}",
"revision": {
"self": "Revisión",
@@ -1894,7 +1894,7 @@
"never-expires": "Nunca caduca",
"role-description": "El rol de un miembro determina qué puede hacer en el proyecto.",
"role-never-expires": "Este rol nunca expira.",
- "add-more": "Más información",
+ "add-more": "Agregar más",
"condition-name": "Nombre de la condición",
"workspace-level-roles": "Roles a nivel de espacio de trabajo",
"project-level-roles": "Roles a nivel de proyecto",
@@ -2044,12 +2044,12 @@
"tab": {
"context-menu": {
"actions": {
- "close": "Cerca",
+ "close": "Cerrar",
"close-others": "cerrar otros",
- "close-to-the-right": "Cerca de la derecha",
+ "close-to-the-right": "Cerrar a la derecha",
"close-saved": "Cerrar guardado",
- "close-all": "Cierra todo",
- "rename": "Rebautizar",
+ "close-all": "Cerrar todo",
+ "rename": "Renombrar",
"add-folder": "Agregar carpeta",
"add-worksheet": "Agregar hoja de trabajo",
"multi-select": "Selección múltiple"
@@ -2150,7 +2150,7 @@
"drop-column": "Eliminar columna",
"create-procedure": "Crear procedimiento",
"create-function": "Crear función",
- "drop": "Gota",
+ "drop": "Eliminar",
"create-view": "Crear vista"
},
"database": {
@@ -2214,8 +2214,8 @@
"add-sub-partition": "Agregar subpartición",
"type": "Tipo"
},
- "views": "Puntos de vista",
- "procedures": "Trámites",
+ "views": "Vistas",
+ "procedures": "Procedimientos",
"functions": "Funciones",
"preview-schema-text": "Vista previa del texto del esquema",
"preview-view-definition": "Definición de vista previa"
@@ -2789,10 +2789,10 @@
"branch": {
"select-tables-to-rollout": "Seleccionar tablas para implementar",
"index": {
- "drop-index-confirm": "¿Índice de caída?"
+ "drop-index-confirm": "¿Eliminar índice?"
},
"table-partition": {
- "drop-partition-confirm": "¿Eliminar partición de mesa?",
+ "drop-partition-confirm": "¿Eliminar partición de tabla?",
"drop-partition-with-subpartitions-confirm": "También eliminará todas sus subparticiones."
}
},
diff --git a/frontend/src/locales/ja-JP.json b/frontend/src/locales/ja-JP.json
index 8250908180..746ab18fcd 100644
--- a/frontend/src/locales/ja-JP.json
+++ b/frontend/src/locales/ja-JP.json
@@ -56,7 +56,7 @@
"approve": "承認する",
"done": "仕上げる",
"create": "作成する",
- "run": "走る",
+ "run": "実行",
"retry": "リトライ",
"skip": "飛び越える",
"skipped": "スキップ",
@@ -87,7 +87,7 @@
"updated-at": "更新日時",
"statement": "ステートメント",
"snapshot": "スナップショット",
- "status": "州",
+ "status": "ステータス",
"stage": "ステージ",
"task": "タスク",
"sql": "SQL",
@@ -201,7 +201,7 @@
"members": "メンバー | メンバー",
"warehouse": "倉庫",
"schedule": "プラン",
- "state": "州",
+ "state": "ステート",
"condition": "状態",
"info": "情報",
"minutes": "分",
@@ -364,7 +364,7 @@
"latest-logs": "最新のログ",
"latest": "最新の実行",
"status": {
- "enqueued": "処刑を待っています。",
+ "enqueued": "実行を待っています。",
"enqueued-with-rollout-time": "実行を待機しています。{time} の後に実行されます。",
"waiting-max-tasks-per-rollout": "他のタスクが完了するのを待っています。ロールアウトごとの最大実行タスク数制限に達しました。最後の報告は {time} です。"
},
@@ -987,7 +987,7 @@
"description": "プロジェクトでフィルターする"
},
"instance": {
- "title": "例",
+ "title": "インスタンス",
"description": "インスタンスによるフィルター"
},
"environment": {
@@ -1142,13 +1142,14 @@
"overview": {
"no-checks": "チェックなし"
},
+ "run": "チェックを実行",
"navigator": {
"changes": "変更点",
- "checks": "小切手",
+ "checks": "チェック",
"statement-empty": "ステートメントが空です"
},
"checks": {
- "self": "小切手",
+ "self": "チェック",
"no-results-match-filters": "フィルターに一致する結果がありません",
"no-check-results": "チェック結果がありません"
},
@@ -1208,7 +1209,7 @@
"last-refresh": "最終更新: {time}"
},
"state": {
- "description": "州別にプランをフィルタリング",
+ "description": "ステータスでプランをフィルタリング",
"close-confirm": "このプランを閉じてもよろしいですか?",
"reopen-confirm": "このプランを再開してもよろしいですか?"
},
@@ -1298,7 +1299,7 @@
},
"triggers": "トリガー",
"trigger": {
- "body": "体",
+ "body": "本文",
"timing": "タイミング",
"event": "イベント"
},
@@ -1330,7 +1331,7 @@
"restore-instance-instance-name-to-normal-state": "インスタンス '{0}' を通常の状態に復元しますか?",
"account-locator": "アカウントロケーター",
"host-or-socket": "ホストまたはソケット",
- "endpoint": "終点",
+ "endpoint": "エンドポイント",
"project-id": "プロジェクトID",
"instance-id": "インスタンスID",
"your-snowflake-account-locator": "Snowflake アカウント ロケーター",
@@ -1519,8 +1520,7 @@
"create": "環境を作成する",
"reorder": "環境の並べ替え",
"successfully-updated-environment": "環境「{name}」は正常に更新されました",
- "production-environment": "本番環境",
- "statement-execution": {}
+ "production-environment": "本番環境"
},
"quick-start": {
"self": "クイックスタート",
@@ -1633,7 +1633,7 @@
"batch-action-disabled-for-unassigned": "未割り当てのデータベース {action} にアクセスできません",
"successfully-transferred-databases": "データベースの移行が完了しました",
"nullable": "null も可能",
- "expression": "表現",
+ "expression": "式",
"unique": "個性的",
"visible": "見える",
"comment": "コメント",
@@ -1641,8 +1641,8 @@
"row-count-estimate": "推定行数",
"data-size": "データサイズ",
"index-size": "インデックスサイズ",
- "column": "リスト",
- "columns": "リスト",
+ "column": "カラム",
+ "columns": "カラム",
"indexes": "索引",
"row-count-est": "推定行数",
"incorrect-project-warning": "SQL エディターは、ユーザーが使用できるプロジェクト内のデータベースのみをクエリできます。まず、このデータベースを作業中のプロジェクトに転送する必要があります。",
@@ -1968,8 +1968,8 @@
"connection-type": "接続タイプ",
"additional-node-addresses": "追加のノードアドレス",
"replica-set": "レプリカセット",
- "admin": "メインライブラリ",
- "read-only": "図書館から",
+ "admin": "管理者",
+ "read-only": "読み取り専用",
"direct-connection": "Direct Connection",
"select-query-data-source": "クエリデータソースの選択"
},
@@ -2168,7 +2168,7 @@
"select": "テーブルの選択",
"name": "テーブル名"
},
- "columns": "リスト",
+ "columns": "カラム",
"column": {
"select": "列を選択",
"name": "名前",
@@ -2210,7 +2210,7 @@
"partitions": "パーティション",
"edit-partitions": "パーティションの編集",
"expression": "表現",
- "value": "価値",
+ "value": "値",
"add-sub-partition": "サブパーティションの追加",
"type": "タイプ"
},
@@ -2284,7 +2284,7 @@
"description": "ライセンスが有効かどうかを確認してください"
}
},
- "plan-features": "{plan} 関数",
+ "plan-features": "{plan} の機能",
"overuse-warning": "{neededPlan} は {currentPlan} で制限されます。通常どおり使用できるように、できるだけ早くアップグレードしてください。",
"overuse-modal": {
"description": "現在「{plan}」に含まれていない機能を使用しています。使用に影響を与えないように、すぐにアップグレードしてください。"
@@ -2406,14 +2406,14 @@
"method": "方法",
"request": "リクエスト",
"response": "応答",
- "status": "ポジション",
+ "status": "ステータス",
"latency": "遅延",
"service-data": "サービスデータ"
},
"advanced-search": {
"scope": {
"actor": {
- "title": "俳優",
+ "title": "実行者",
"description": "監査ログアクターによる検索"
},
"method": {
@@ -2541,7 +2541,7 @@
"history-conversations": "歴史対話",
"view-history-conversations": "過去の会話を表示する",
"new-conversation": "新しい会話を開始する",
- "no-message": "ニュースはありません",
+ "no-message": "この会話にはメッセージはありません",
"tips": {
"suggest-prompt": "プロンプト単語を生成...",
"no-more": "何も残っていない"
@@ -2587,7 +2587,7 @@
"node": {
"nodes": "承認ノード",
"description": "ノードに複数の承認者がいる場合、必要な承認は 1 つだけです。",
- "order": "注文",
+ "order": "順序",
"approver": "承認者",
"add": "ノードの追加",
"delete": "承認ノードの削除"
diff --git a/frontend/src/locales/sql-review/en-US.json b/frontend/src/locales/sql-review/en-US.json
index 643f61f3fe..f571e4edab 100644
--- a/frontend/src/locales/sql-review/en-US.json
+++ b/frontend/src/locales/sql-review/en-US.json
@@ -48,7 +48,7 @@
},
"COLUMN_AUTO_INCREMENT_INITIAL_VALUE": {
"title": "Restrict the initial value of auto-increment columns",
- "description": "based on management requirements to limit the initial value of the auto-increment column. Suggestion error level: Warning",
+ "description": "based on management requirements to limit the initial value of the auto-increment column. Suggested error level: Warning",
"component": {
"number": {
"title": "Initial value"
@@ -77,7 +77,7 @@
},
"COLUMN_CURRENT_TIME_COUNT_LIMIT": {
"title": "Restrict the number of columns in the table that acquire system time",
- "description": "Only columns recording the creation time of the record with \"DEFAULT NOW()\" and recording the update time of the record with \"DEFAULT NOW() ON UPDATE\" need to call function to get system time. It is meaningless and will increase resource overhead to record system time in other columns. Suggestion error level: Error"
+ "description": "Only columns recording the creation time of the record with \"DEFAULT NOW()\" and recording the update time of the record with \"DEFAULT NOW() ON UPDATE\" need to call function to get system time. It is meaningless and will increase resource overhead to record system time in other columns. Suggested error level: Error"
},
"COLUMN_DEFAULT_DISALLOW_VOLATILE": {
"title": "Disallow setting volatile default value on columns",
@@ -109,7 +109,7 @@
},
"COLUMN_MAXIMUM_CHARACTER_LENGTH": {
"title": "Restrict the length of \"CHAR\" data type",
- "description": "\"CHAR\" is a fixed-length type. For example, the CHAR(20) column will occupy 20 character spaces even if only one character is stored, causing waste. When the string is too long and the length is not fixed, consider using VARCHAR for MySQL and using TEXT for PostgreSQL. Suggestion error level: Error",
+ "description": "\"CHAR\" is a fixed-length type. For example, the CHAR(20) column will occupy 20 character spaces even if only one character is stored, causing waste. When the string is too long and the length is not fixed, consider using VARCHAR for MySQL and using TEXT for PostgreSQL. Suggested error level: Error",
"component": {
"number": {
"title": "Maximum length"
@@ -140,15 +140,15 @@
},
"COLUMN_REQUIRE_CHARSET": {
"title": "Require charset for text columns",
- "description": "The charset of columns with text data types must be specified. Suggestion error level: Warning"
+ "description": "The charset of columns with text data types must be specified. Suggested error level: Warning"
},
"COLUMN_REQUIRE_COLLATION": {
"title": "Require collation for text columns",
- "description": "The collation of columns with text data types must be specified. Suggestion error level: Warning"
+ "description": "The collation of columns with text data types must be specified. Suggested error level: Warning"
},
"COLUMN_REQUIRE_DEFAULT": {
"title": "Enforce setting default value on columns",
- "description": "Setting default values that satisfy business logic can effectively improve the data quality of downstream analytical pipeline. This rule does not check \"PRIMARY KEY\", \"JSON\", \"BLOB\", \"TEXT\", \"GEOMETRY\", \"AUTO_INCREMENT\", \"GENERATED\" types. Suggestion error level: Warning"
+ "description": "Setting default values that satisfy business logic can effectively improve the data quality of downstream analytical pipeline. This rule does not check \"PRIMARY KEY\", \"JSON\", \"BLOB\", \"TEXT\", \"GEOMETRY\", \"AUTO_INCREMENT\", \"GENERATED\" types. Suggested error level: Warning"
},
"COLUMN_SET_DEFAULT_FOR_NOT_NULL": {
"title": "Enforce default value on \"NOT NULL\" columns",
@@ -169,15 +169,15 @@
},
"ENGINE_MYSQL_USE_INNODB": {
"title": "Enforce InnoDB storage engine",
- "description": "InnoDB is the default storage engine for MySQL that provides transaction support. It also provides better performance for high-concurrency and low-latency scenarios, and supports online data backup and recovery. It is the preferred choice for OLTP businesses. Suggestion error level: Error"
+ "description": "InnoDB is the default storage engine for MySQL that provides transaction support. It also provides better performance for high-concurrency and low-latency scenarios, and supports online data backup and recovery. It is the preferred choice for OLTP businesses. Suggested error level: Error"
},
"INDEX_CREATE_CONCURRENTLY": {
"title": "Enforce concurrent index creation",
- "description": "In PostgreSQL 11 and above, using the standard statement to create an index will cause table locking and unable to write. Using the \"CONCURRENTLY\" mode can avoid this problem. Suggestion error level: Warning"
+ "description": "In PostgreSQL 11 and above, using the standard statement to create an index will cause table locking and unable to write. Using the \"CONCURRENTLY\" mode can avoid this problem. Suggested error level: Warning"
},
"INDEX_KEY_NUMBER_LIMIT": {
"title": "Restrict the number of columns in a single index",
- "description": "A composite index with over 5 columns does not significantly improve query performance, but it occupies a lot of space and reduces DML performance. Suggestion error level: Warning",
+ "description": "A composite index with over 5 columns does not significantly improve query performance, but it occupies a lot of space and reduces DML performance. Suggested error level: Warning",
"component": {
"number": {
"title": "Maximum column count"
@@ -186,11 +186,11 @@
},
"INDEX_NOT_REDUNDANT": {
"title": "Disallow redundant indexes",
- "description": "Redundant index may result in performance loss and occupy additional space. For example, the index on columns (c1, c2) will be treated as redundant indexes if there is already a index on column (c1). Suggestion error level: Warning"
+ "description": "Redundant index may result in performance loss and occupy additional space. For example, the index on columns (c1, c2) will be treated as redundant indexes if there is already a index on column (c1). Suggested error level: Warning"
},
"INDEX_NO_DUPLICATE_COLUMN": {
"title": "Prohibit indexes containing duplicate columns",
- "description": "Creating an index with duplicate columns will result in failure. Suggestion error level: Error"
+ "description": "Creating an index with duplicate columns will result in failure. Suggested error level: Error"
},
"INDEX_PK_TYPE_LIMIT": {
"title": "Primary key type limit",
@@ -198,7 +198,7 @@
},
"INDEX_PRIMARY_KEY_TYPE_ALLOWLIST": {
"title": "Allowable list of primary key types",
- "description": "The appropriate primary key type can optimize storage structure, reduce space usage, and beneficial for insert and query performance. Suggestion error level: Warning",
+ "description": "The appropriate primary key type can optimize storage structure, reduce space usage, and beneficial for insert and query performance. Suggested error level: Warning",
"component": {
"list": {
"title": "Allow list"
@@ -207,7 +207,7 @@
},
"INDEX_TOTAL_NUMBER_LIMIT": {
"title": "Restrict the number of indexes on a single table",
- "description": "Although indexes can improve query performance, they also occupy a lot of space and reduce DML performance. Therefore, it is not recommended to create more than 5 indexes in a table. Suggestion error level: Warning",
+ "description": "Although indexes can improve query performance, they also occupy a lot of space and reduce DML performance. Therefore, it is not recommended to create more than 5 indexes in a table. Suggested error level: Warning",
"component": {
"number": {
"title": "Maximum index count"
@@ -216,7 +216,7 @@
},
"INDEX_TYPE_ALLOW_LIST": {
"title": "Allowable list of index types",
- "description": "Different index types have different performance characteristics. For example, B-tree indexes are suitable for range queries, while hash indexes are suitable for equality queries. Suggestion error level: Warning",
+ "description": "Different index types have different performance characteristics. For example, B-tree indexes are suitable for range queries, while hash indexes are suitable for equality queries. Suggested error level: Warning",
"component": {
"list": {
"title": "Allow list"
@@ -225,11 +225,11 @@
},
"INDEX_TYPE_NO_BLOB": {
"title": "Prohibit creating indexes on \"BLOB\" and \"TEXT\" data type columns",
- "description": "The \"BLOB\" type is usually used to store binary data and should not be used as a query condition. If an index is created on this column type by mistake, it will consume a lot of resources and cause serious performance impact. Suggestion error level: Error"
+ "description": "The \"BLOB\" type is usually used to store binary data and should not be used as a query condition. If an index is created on this column type by mistake, it will consume a lot of resources and cause serious performance impact. Suggested error level: Error"
},
"NAMING_COLUMN": {
"title": "Enforce column naming format",
- "description": "The default format is all lowercase letters, separated by underscores between words, which is no more than 63 characters long, such as \"abc\" and \"abc_def\". Suggestion error level: Warning",
+ "description": "The default format is all lowercase letters, separated by underscores between words, which is no more than 63 characters long, such as \"abc\" and \"abc_def\". Suggested error level: Warning",
"component": {
"format": {
"title": "Column name format (regex)"
@@ -270,7 +270,7 @@
},
"NAMING_INDEX_FK": {
"title": "Enforce foreign key naming format",
- "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"fk_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"fk_my_table_id_name\". Suggestion error level: Warning",
+ "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"fk_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"fk_my_table_id_name\". Suggested error level: Warning",
"component": {
"format": {
"title": "Foreign key name format",
@@ -288,7 +288,7 @@
},
"NAMING_INDEX_IDX": {
"title": "Enforce index naming format",
- "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"idx_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"idx_my_table_id_name\". Suggestion error level: Warning",
+ "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"idx_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"idx_my_table_id_name\". Suggested error level: Warning",
"component": {
"format": {
"title": "Index name format",
@@ -304,7 +304,7 @@
},
"NAMING_INDEX_PK": {
"title": "Enforce primary key naming format",
- "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"pk_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"pk_my_table_id_name\". Suggestion error level: Warning",
+ "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"pk_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"pk_my_table_id_name\". Suggested error level: Warning",
"component": {
"format": {
"title": "Primary key name format",
@@ -320,7 +320,7 @@
},
"NAMING_INDEX_UK": {
"title": "Enforce unique key naming format",
- "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"uk_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"uk_my_table_id_name\". Suggestion error level: Warning",
+ "description": "The name is allowed to be empty and named by the database. If not empty, the default format is \"uk_<table name>_<unique key column name combination>\", which is no more than 63 characters long, such as \"uk_my_table_id_name\". Suggested error level: Warning",
"component": {
"format": {
"title": "Unique key name format",
@@ -336,7 +336,7 @@
},
"NAMING_TABLE": {
"title": "Enforce table naming format",
- "description": "The default format is all lowercase letters, separated by underscores between words, and no more than 63 characters long, such as \"abc\" and \"abc_def\". Suggestion error level: Warning",
+ "description": "The default format is all lowercase letters, separated by underscores between words, and no more than 63 characters long, such as \"abc\" and \"abc_def\". Suggested error level: Warning",
"component": {
"format": {
"title": "Table name format (regex)"
@@ -352,11 +352,11 @@
},
"SCHEMA_BACKWARD_COMPATIBILITY": {
"title": "Check application backward compatibility",
- "description": "Some changes may affect running applications, such as modifying the name of database object, adding new constraints, etc. This rule can avoid careless changes that lead to the failure of existing application. Suggestion error level: Warning"
+ "description": "Some changes may affect running applications, such as modifying the name of database object, adding new constraints, etc. This rule can avoid careless changes that lead to the failure of existing application. Suggested error level: Warning"
},
"STATEMENT_ADD_CHECK_NOT_VALID": {
"title": "Enforce including \"NOT VALID\" option when adding \"CHECK\" constraints",
- "description": "Adding a CHECK constraint needs to verify the existing data and requires ACCESS EXCLUSIVE table lock. This blocks read and write, which may cause business interruption. It is recommended to add the \"NOT VALID\" option to validate new data and manually validate existing data after the change is completed. Suggestion error level: Warning"
+ "description": "Adding a CHECK constraint needs to verify the existing data and requires ACCESS EXCLUSIVE table lock. This blocks read and write, which may cause business interruption. It is recommended to add the \"NOT VALID\" option to validate new data and manually validate existing data after the change is completed. Suggested error level: Warning"
},
"STATEMENT_ADD_COLUMN_WITHOUT_POSITION": {
"title": "Check no position in ADD COLUMN clause",
@@ -364,11 +364,11 @@
},
"STATEMENT_ADD_FOREIGN_KEY_NOT_VALID": {
"title": "Enforce including \"NOT VALID\" option when adding foreign keys",
- "description": "Adding foreign keys needs to verify the existing data and requires SHARE ROW EXCLUSIVE table lock. This blocks write, which may cause business interruption. It is recommended to add the \"NOT VALID\" option to validate new data and validate existing data after the change is completed. Suggestion error level: Warning"
+ "description": "Adding foreign keys needs to verify the existing data and requires SHARE ROW EXCLUSIVE table lock. This blocks write, which may cause business interruption. It is recommended to add the \"NOT VALID\" option to validate new data and validate existing data after the change is completed. Suggested error level: Warning"
},
"STATEMENT_AFFECTED_ROW_LIMIT": {
"title": "Restrict the maximum number of updated or deleted rows (estimated).",
- "description": "Reveal the number of rows to be updated or deleted can help determine whether the statement meets business expectations. Suggestion error level: Warning",
+ "description": "Reveal the number of rows to be updated or deleted can help determine whether the statement meets business expectations. Suggested error level: Warning",
"component": {
"number": {
"title": "Maximum affected rows"
@@ -377,7 +377,7 @@
},
"STATEMENT_CHECK_SET_ROLE_VARIABLE": {
"title": "Check if Set Role statement at the beginning",
- "description": "Failure to set the role statement properly at the beginning of a session may lead to unauthorized access or improper permissions assignment, potentially compromising data security and integrity. Suggestion error level: Warning"
+ "description": "Failure to set the role statement properly at the beginning of a session may lead to unauthorized access or improper permissions assignment, potentially compromising data security and integrity. Suggested error level: Warning"
},
"STATEMENT_CREATE_SPECIFY_SCHEMA": {
"title": "Prohibit creating objects without specifying the schema",
@@ -385,15 +385,15 @@
},
"STATEMENT_DISALLOW_ADD_COLUMN_WITH_DEFAULT": {
"title": "Restrict adding columns with default values to a table",
- "description": "Before PostgreSQL 11, adding a column with a default value cause table locking and unable to read and write, which may cause business interruption. In PostgreSQL 11 and above, this issue has been optimized and there is no need to pay attention to this rule. Suggestion error level: Warning"
+ "description": "Before PostgreSQL 11, adding a column with a default value cause table locking and unable to read and write, which may cause business interruption. In PostgreSQL 11 and above, this issue has been optimized and there is no need to pay attention to this rule. Suggested error level: Warning"
},
"STATEMENT_DISALLOW_ADD_NOT_NULL": {
"title": "Restrict adding \"NOT NULL\" constraint to existing columns",
- "description": "Adding NOT NULL constraint with default value before PostgreSQL 11 or adding NOT NULL constraint without default value requires to verify the existing data. This blocks read and write, which may cause business interruption. Suggestion error level: Warning"
+ "description": "Adding NOT NULL constraint with default value before PostgreSQL 11 or adding NOT NULL constraint without default value requires to verify the existing data. This blocks read and write, which may cause business interruption. Suggested error level: Warning"
},
"STATEMENT_DISALLOW_COMMIT": {
"title": "Prohibit explicit \"COMMIT\" statement",
- "description": "In some cases, multiple statements are required to be included in a transaction committed by the system, in order to quickly rerun in case of partial failure. Therefore, explicit \"COMMIT\" is not allowed. Suggestion error level: Warning"
+ "description": "In some cases, multiple statements are required to be included in a transaction committed by the system, in order to quickly rerun in case of partial failure. Therefore, explicit \"COMMIT\" is not allowed. Suggested error level: Warning"
},
"STATEMENT_DISALLOW_CROSS_DB_QUERIES": {
"title": "Disallow cross database queries",
@@ -401,7 +401,7 @@
},
"STATEMENT_DISALLOW_LIMIT": {
"title": "Prohibit using \"LIMIT\" clause in DML statements",
- "description": "If LIMIT is used in DML statements without an ORDER BY clause, the affected rows order are not fixed, which may cause data inconsistency between the primary and replica databases in some replication modes. Suggestion error level: Error"
+ "description": "If LIMIT is used in DML statements without an ORDER BY clause, the affected rows order are not fixed, which may cause data inconsistency between the primary and replica databases in some replication modes. Suggested error level: Error"
},
"STATEMENT_DISALLOW_OFFLINE_DDL": {
"title": "Disallow Offline DDL",
@@ -409,39 +409,39 @@
},
"STATEMENT_DISALLOW_ON_DEL_CASCADE": {
"title": "Prohibit using CASCADE option for ON DELETE clauses",
- "description": "The \"CASCADE\" option in 'ON DELETE' can cause a large number of dependent objects to be deleted or modified, which may cause unexpected results. Suggestion error level: Error"
+ "description": "The \"CASCADE\" option in 'ON DELETE' can cause a large number of dependent objects to be deleted or modified, which may cause unexpected results. Suggested error level: Error"
},
"STATEMENT_DISALLOW_ORDER_BY": {
"title": "Prohibit using \"ORDER BY\" clause in \"UPDATE\" and \"DELETE\" statements",
- "description": "Sorting operations are extremely resource-intensive, so for update and delete operations, it is recommended to use a deterministic filtering condition as much as possible instead of using ORDER BY and LIMIT. Suggestion error level: Error"
+ "description": "Sorting operations are extremely resource-intensive, so for update and delete operations, it is recommended to use a deterministic filtering condition as much as possible instead of using ORDER BY and LIMIT. Suggested error level: Error"
},
"STATEMENT_DISALLOW_RM_TBL_CASCADE": {
"title": "Prohibit using CASCADE when removing a table",
- "description": "Using the \"CASCADE\" option when removing a table can cause a large number of dependent objects to be deleted or modified, which may cause unexpected results. Suggestion error level: Error"
+ "description": "Using the \"CASCADE\" option when removing a table can cause a large number of dependent objects to be deleted or modified, which may cause unexpected results. Suggested error level: Error"
},
"STATEMENT_DISALLOW_USING_FILESORT": {
"title": "Prohibit using filesort",
- "description": "Filesort is a resource-intensive operation and may cause serious performance impact. Suggestion error level: Warning"
+ "description": "Filesort is a resource-intensive operation and may cause serious performance impact. Suggested error level: Warning"
},
"STATEMENT_DISALLOW_USING_TEMPORARY": {
"title": "Prohibit using temporary tables",
- "description": "Temporary tables are not recommended for use in production environments. They can cause resource contention and performance issues. Suggestion error level: Warning"
+ "description": "Temporary tables are not recommended for use in production environments. They can cause resource contention and performance issues. Suggested error level: Warning"
},
"STATEMENT_DML_DRY_RUN": {
"title": "Validate the executability of DML statements",
- "description": "When the syntax is correct, but the table name is incorrect or the permission is insufficient, it can be discovered by dry run before the actual execution. Suggestion error level: Warning"
+ "description": "When the syntax is correct, but the table name is incorrect or the permission is insufficient, it can be discovered by dry run before the actual execution. Suggested error level: Warning"
},
"STATEMENT_INSERT_DISALLOW_ORDER_BY_RAND": {
"title": "Prohibit using \"ORDER BY rand()\" in \"INSERT\" statement",
- "description": "Randomly sorting the data to be inserted is meaningless and will only consume uncessary resources. Suggestion error level: Error"
+ "description": "Randomly sorting the data to be inserted is meaningless and will only consume unnecessary resources. Suggested error level: Error"
},
"STATEMENT_INSERT_MUST_SPECIFY_COLUMN": {
"title": "Enforce specifying column names in \"INSERT\" statements",
- "description": "The \"INSERT INTO table VALUES (...)\" statement does not explicit list column names. Once the column order changes or columns are added or dropped, the statement may faile or generate unexpected data. Suggestion error level: Error"
+ "description": "The \"INSERT INTO table VALUES (...)\" statement does not explicit list column names. Once the column order changes or columns are added or dropped, the statement may fail or generate unexpected data. Suggested error level: Error"
},
"STATEMENT_INSERT_ROW_LIMIT": {
"title": "Restrict the maximum number of inserted rows",
- "description": "Reveal the number of rows to be inserted can help determine whether the statement meets business expectations. Suggestion error level: Warning",
+ "description": "Reveal the number of rows to be inserted can help determine whether the statement meets business expectations. Suggested error level: Warning",
"component": {
"number": {
"title": "Maximum insert amount"
@@ -481,19 +481,19 @@
},
"STATEMENT_MAX_EXECUTION_TIME": {
"title": "Enforce set the max execution time parameter",
- "description": "Set the maximum execution time for SQL statements. If the execution time exceeds the limit, the statement will be terminated. Suggestion error level: Warning",
+ "description": "Set the maximum execution time for SQL statements. If the execution time exceeds the limit, the statement will be terminated. Suggested error level: Warning",
"mysql": {
"title": "Enforce set the MAX_EXECUTION_TIME parameter explicitly",
- "description": "Set the MAX_EXECUTION_TIME parameter in the change script to explicitly control the maximum execution time of the statement. Suggestion error level: Warning"
+ "description": "Set the MAX_EXECUTION_TIME parameter in the change script to explicitly control the maximum execution time of the statement. Suggested error level: Warning"
},
"mariadb": {
"title": "Enforce set the MAX_STATEMENT_TIME parameter explicitly",
- "description": "Set the MAX_STATEMENT_TIME parameter in the change script to explicitly control the maximum execution time of the statement. Suggestion error level: Warning"
+ "description": "Set the MAX_STATEMENT_TIME parameter in the change script to explicitly control the maximum execution time of the statement. Suggested error level: Warning"
}
},
"STATEMENT_MERGE_ALTER_TABLE": {
"title": "Prohibit issuing multiple independent changes on the same table",
- "description": "Every change to a table may cause a table-level lock and consume a large amount of resources. If there are multiple changes to the same table, they should be merged into a single change statement. Suggestion error level: Error"
+ "description": "Every change to a table may cause a table-level lock and consume a large amount of resources. If there are multiple changes to the same table, they should be merged into a single change statement. Suggested error level: Error"
},
"STATEMENT_NON_TRANSACTIONAL": {
"title": "Detect and report non-transactional statements",
@@ -522,11 +522,11 @@
},
"STATEMENT_SELECT_FULL_TABLE_SCAN": {
"title": "Check full table scan for queries",
- "description": "Full table scan is a resource-intensive operation and may cause serious performance impact. Suggestion error level: Error"
+ "description": "Full table scan is a resource-intensive operation and may cause serious performance impact. Suggested error level: Error"
},
"STATEMENT_SELECT_NO_SELECT_ALL": {
"title": "Prohibit using \"SELECT *\"",
- "description": "SELECT * to fetch entire row data may cause unnecessary resource overhead and may also cause unexpected results in applications once the table adds or removes columns. Suggestion error level: Error"
+ "description": "SELECT * to fetch entire row data may cause unnecessary resource overhead and may also cause unexpected results in applications once the table adds or removes columns. Suggested error level: Error"
},
"STATEMENT_WHERE_DISALLOW_FUNCTIONS_AND_CALCULATIONS": {
"title": "Do not apply functions or perform calculations on indexed fields in the WHERE clause",
@@ -543,19 +543,19 @@
},
"STATEMENT_WHERE_NO_EQUAL_NULL": {
"title": "Prohibit using NULL equality comparison in WHERE clause",
- "description": "The result of NULL equality comparison is always NULL, which may cause unexpected results. Suggestion error level: Warning"
+ "description": "The result of NULL equality comparison is always NULL, which may cause unexpected results. Suggested error level: Warning"
},
"STATEMENT_WHERE_NO_LEADING_WILDCARD_LIKE": {
"title": "Prohibit using leading wildcard in filter conditions",
- "description": "When using leading wildcard, such as \"LIKE '%ABC'\", the database optimizer cannot use fast index scan, and fallback to full table scan or full index scan, which may cause serious performance impact. Suggestion error level: Error"
+ "description": "When using leading wildcard, such as \"LIKE '%ABC'\", the database optimizer cannot use fast index scan, and fallback to full table scan or full index scan, which may cause serious performance impact. Suggested error level: Error"
},
"STATEMENT_WHERE_REQUIRE_SELECT": {
"title": "Enforce the presence of \"WHERE\" condition in SELECT statements",
- "description": "Queries without WHERE clause may cause huge uncessary resource overhead. Suggestion error level: Error"
+ "description": "Queries without WHERE clause may cause huge unnecessary resource overhead. Suggested error level: Error"
},
"STATEMENT_WHERE_REQUIRE_UPDATE_DELETE": {
- "title": "Enforce the presence of \"WHERE\" condition in UDPATE/DELETE statements",
- "description": "DMLs without WHERE clause may cause massive accidental data loss. Suggestion error level: Error"
+ "title": "Enforce the presence of \"WHERE\" condition in UPDATE/DELETE statements",
+ "description": "DMLs without WHERE clause may cause massive accidental data loss. Suggested error level: Error"
},
"SYSTEM_CHARSET_ALLOWLIST": {
"title": "Allowable list of Charset",
@@ -623,7 +623,7 @@
},
"TABLE_DISALLOW_DDL": {
"title": "Disallow DDL",
- "description": "Configure which tables are prohibited from executing DDL. Suggestion error level: Warning",
+ "description": "Configure which tables are prohibited from executing DDL. Suggested error level: Warning",
"component": {
"list": {
"title": "Table names"
@@ -632,7 +632,7 @@
},
"TABLE_DISALLOW_DML": {
"title": "Disallow DML",
- "description": "Configure which tables are prohibited from executing DML. Suggestion error level: Warning",
+ "description": "Configure which tables are prohibited from executing DML. Suggested error level: Warning",
"component": {
"list": {
"title": "Table names"
@@ -641,7 +641,7 @@
},
"TABLE_DISALLOW_PARTITION": {
"title": "Prohibit using partition table",
- "description": "In some database engines, partitioned tables are not mature, and the use and maintenance are inconvenient. Therefore, it is more inclined to use manual data partitioning methods such as database and table sharding. Suggestion error level: Warning"
+ "description": "In some database engines, partitioned tables are not mature, and the use and maintenance are inconvenient. Therefore, it is more inclined to use manual data partitioning methods such as database and table sharding. Suggested error level: Warning"
},
"TABLE_DISALLOW_SET_CHARSET": {
"title": "Prohibit defining character set in table properties",
@@ -649,11 +649,11 @@
},
"TABLE_DISALLOW_TRIGGER": {
"title": "Prevent the use of triggers on tables",
- "description": "This rule restricts the usage of triggers on tables. Triggers can introduce complexity and potential performance issues to database operations. By disallowing triggers, the system can maintain a simpler and more predictable behavior. Suggestion error level: Warning"
+ "description": "This rule restricts the usage of triggers on tables. Triggers can introduce complexity and potential performance issues to database operations. By disallowing triggers, the system can maintain a simpler and more predictable behavior. Suggested error level: Warning"
},
"TABLE_DROP_NAMING_CONVENTION": {
"title": "Restrict the naming format of tables to be deleted",
- "description": "For example, by requiring the \"_del\" suffix, it can effectively prevent accidental deletions. Suggestion error level: Error",
+ "description": "For example, by requiring the \"_del\" suffix, it can effectively prevent accidental deletions. Suggested error level: Error",
"component": {
"format": {
"title": "Table name format (regex)"
@@ -675,19 +675,19 @@
},
"TABLE_NO_FOREIGN_KEY": {
"title": "Prohibit using foreign key constraints",
- "description": "The advantages and disadvantages of foreign key are highly controversial. Using foreign key may significantly increase the difficulty of database changes, scalability (such as sharding), etc. And may even prevent the use of some tools. Therefore, another option is to implement foreign key constraints at the application layer. Suggestion error level: Warning"
+ "description": "The advantages and disadvantages of foreign key are highly controversial. Using foreign key may significantly increase the difficulty of database changes, scalability (such as sharding), etc. And may even prevent the use of some tools. Therefore, another option is to implement foreign key constraints at the application layer. Suggested error level: Warning"
},
"TABLE_REQUIRE_CHARSET": {
"title": "Require charset",
- "description": "The charset of the table must be specified. Suggestion error level: Warning"
+ "description": "The charset of the table must be specified. Suggested error level: Warning"
},
"TABLE_REQUIRE_COLLATION": {
"title": "Require collation",
- "description": "The collation of the table must be specified. Suggestion error level: Warning"
+ "description": "The collation of the table must be specified. Suggested error level: Warning"
},
"TABLE_REQUIRE_PK": {
"title": "Enforce inclusion of primary key in a table",
- "description": "Various data synchronization, comparison, and rollback tools require tables to have primary key. Suggestion error level: Error"
+ "description": "Various data synchronization, comparison, and rollback tools require tables to have primary key. Suggested error level: Error"
},
"TABLE_TEXT_FIELDS_TOTAL_LENGTH": {
"title": "Restrict the total length of text fields in a table",
diff --git a/frontend/src/locales/sql-review/zh-CN.json b/frontend/src/locales/sql-review/zh-CN.json
index d1cf3a7e0d..3975681df4 100644
--- a/frontend/src/locales/sql-review/zh-CN.json
+++ b/frontend/src/locales/sql-review/zh-CN.json
@@ -671,7 +671,7 @@
},
"TABLE_NO_DUPLICATE_INDEX": {
"title": "禁止表上重复索引",
- "description": "此规则要求表上没有重复索引。重复索引会占用额外的存储空间であり、クエリパフォーマンスを低下させる可能性があります。推奨エラーレベル:警告。"
+ "description": "此规则要求表上没有重复索引。重复索引会占用额外的存储空间,并可能降低查询性能。建议错误等级:警告。"
},
"TABLE_NO_FOREIGN_KEY": {
"title": "禁止使用外键约束",
diff --git a/frontend/src/locales/vi-VN.json b/frontend/src/locales/vi-VN.json
index 0162362806..5ecb40201d 100644
--- a/frontend/src/locales/vi-VN.json
+++ b/frontend/src/locales/vi-VN.json
@@ -174,7 +174,7 @@
"regenerate": "Tạo lại",
"download": "Tải xuống",
"deleted": "Đã xóa",
- "active": "Tích cực",
+ "active": "Hoạt động",
"reopen": "Mở lại",
"plan": "Kế hoạch",
"rollout": "Triển khai",
@@ -242,7 +242,7 @@
"removed": "LOẠI BỎ",
"submit": "Nộp",
"draft": "Bản nháp",
- "import": "Nhập khẩu",
+ "import": "Nhập",
"hard-delete": {
"self": "Xóa cứng",
"title": "Xóa cứng {name}?",
@@ -250,7 +250,7 @@
"double-comfirm": "Để xác nhận xóa, vui lòng nhập: {name}",
"notification": "Xóa thành công tài nguyên '{name}'."
},
- "collapse": "Sụp đổ",
+ "collapse": "Thu gọn",
"show-more": "Hiển thị thêm",
"n-more": "+{n} nữa",
"remaining": "còn lại",
@@ -371,13 +371,13 @@
"rollback": {
"available": "Có thể khôi phục lại cho tác vụ {n} | Có thể khôi phục lại cho tác vụ {n}",
"preview-statement": {
- "self": "Xem trước tuyên bố",
+ "self": "Xem trước câu lệnh",
"description": "Bytebase tạo ra một câu lệnh khôi phục dựa trên tác vụ đang chạy. Bạn có thể xem lại câu lệnh này trước khi thực hiện khôi phục."
},
"no-statement-generated": "Không có câu lệnh khôi phục nào được tạo ra"
},
"log-type": {
- "schema-dump": "Sơ đồ đổ",
+ "schema-dump": "Xuất schema",
"command-execute": "Lệnh thực thi",
"database-sync": "Đồng bộ cơ sở dữ liệu",
"transaction": "Giao dịch",
@@ -387,7 +387,7 @@
"release-file-execute": "Tệp phát hành"
},
"log-detail": {
- "dumping": "đổ rác...",
+ "dumping": "đang xuất...",
"syncing": "đang đồng bộ hóa...",
"backup-completed": "đã hoàn thành ({count} bảng)",
"backing-up": "đang sao lưu...",
@@ -1015,15 +1015,15 @@
"description": "Lọc theo nhãn vấn đề"
},
"table": {
- "title": "bề mặt",
+ "title": "Bảng",
"description": "Nhập giá trị sau đó nhấn Enter"
},
"label": {
"description": "Nhập cặp \"key:value\" rồi nhấn Enter"
},
"engine": {
- "title": "Động cơ",
- "description": "Lọc theo động cơ"
+ "title": "Engine",
+ "description": "Lọc theo engine"
}
}
},
@@ -1122,7 +1122,7 @@
"request-specific-role": "Yêu cầu vai trò \"{role}\""
},
"review": {
- "self": "Ôn tập",
+ "self": "Xem xét",
"comment-description": "Gửi phản hồi chung mà không cần phê duyệt",
"approve-description": "Gửi phản hồi và phê duyệt vấn đề này.",
"reject-description": "Gửi phản hồi và yêu cầu thay đổi"
@@ -1142,6 +1142,7 @@
"overview": {
"no-checks": "Không kiểm tra"
},
+ "run": "Chạy kiểm tra",
"navigator": {
"changes": "Thay đổi",
"checks": "Kiểm tra",
@@ -1498,11 +1499,11 @@
"advanced-search": {
"scope": {
"host": {
- "title": "Chủ nhà",
+ "title": "Host",
"description": "Lọc theo máy chủ lưu trữ. Vui lòng nhập giá trị rồi nhấn Enter."
},
"port": {
- "title": "Cảng",
+ "title": "Port",
"description": "Lọc theo cổng phiên bản. Vui lòng nhập giá trị rồi nhấn Enter."
}
}
@@ -1519,8 +1520,7 @@
"create": "Tạo môi trường",
"reorder": "Sắp xếp lại môi trường",
"successfully-updated-environment": "Đã cập nhật thành công môi trường '{name}'.",
- "production-environment": "Môi trường sản xuất",
- "statement-execution": {}
+ "production-environment": "Môi trường sản xuất"
},
"quick-start": {
"self": "Bắt đầu nhanh",
@@ -1637,7 +1637,7 @@
"unique": "Duy nhất",
"visible": "Hiển thị",
"comment": "Bình luận",
- "engine": "Động cơ",
+ "engine": "Engine",
"row-count-estimate": "Ước tính số hàng",
"data-size": "Kích thước dữ liệu",
"index-size": "Kích thước chỉ mục",
@@ -1735,7 +1735,7 @@
"content-preview": "Xem trước nội dung",
"revision-type": "Loại sửa đổi",
"type-versioned": "Phiên bản",
- "type-declarative": "Tuyên bố",
+ "type-declarative": "Khai báo",
"invalid-version-format": "Phiên bản phải là các phần số được phân tách bằng dấu chấm (ví dụ: 1.0.0)",
"version-already-exists": "Phiên bản này đã tồn tại trong cơ sở dữ liệu",
"delete-confirm-dialog": "Thao tác này sẽ xóa các bản sửa đổi đã áp dụng này và lược đồ cơ sở dữ liệu sẽ không bị thay đổi. Hành động này không thể hoàn tác."
@@ -2155,7 +2155,7 @@
},
"database": {
"name": "Tên",
- "engine": "Động cơ",
+ "engine": "Engine",
"collation": "Đối chiếu",
"comment": "Bình luận"
},
@@ -2756,7 +2756,7 @@
}
},
"release": {
- "title": "Giải phóng",
+ "title": "Phát hành",
"releases": "Bản phát hành",
"files": "Tệp",
"total-files": "Tổng số {count} tệp",
diff --git a/frontend/src/locales/zh-CN.json b/frontend/src/locales/zh-CN.json
index dd970ce147..312e29dca3 100644
--- a/frontend/src/locales/zh-CN.json
+++ b/frontend/src/locales/zh-CN.json
@@ -44,7 +44,7 @@
"archived": "已归档",
"abandon": "废弃",
"abandoned": "已废弃",
- "restored": "Restored",
+ "restored": "已恢复",
"no-license": "无证书",
"logout": "登出",
"close": "关闭",
@@ -259,13 +259,13 @@
"apply-to-database": "应用到数据库",
"unlimited": "无限制",
"unknown": "未知",
- "danger-zone": "Danger Zone",
- "archive-resource": "Archive {type}",
- "delete-resource": "Delete {type}",
- "confirm-archive": "Archive Resource?",
- "confirm-delete": "Delete Resource?",
- "archive-description": "Mark \"{name}\" as archived and read-only.",
- "delete-resource-description": "Once you delete \"{name}\", there is no going back. Please be certain."
+ "danger-zone": "危险区域",
+ "archive-resource": "归档{type}",
+ "delete-resource": "删除{type}",
+ "confirm-archive": "确定归档资源?",
+ "confirm-delete": "确定删除资源?",
+ "archive-description": "将「{name}」标记为已归档且只读。",
+ "delete-resource-description": "删除「{name}」后将无法恢复,请确认。"
},
"error-page": {
"go-back-home": "回到主页"
@@ -404,8 +404,8 @@
},
"banner": {
"license-expired": "您的{plan}证书已在 {expireAt} 过期",
- "license-expires": "您的{plan}证书将在 {days} 天后过期",
- "trial-expires": "您的{plan}试用将在 {days} 天后过期",
+ "license-expires": "您的{plan}证书将在 {days} 天后({expireAt})过期",
+ "trial-expires": "您的{plan}试用将在 {days} 天后({expireAt})过期",
"deploy": "本地部署",
"cloud": "云服务",
"request-demo": "预约一个 30 分钟的产品演示。",
@@ -1142,6 +1142,7 @@
"overview": {
"no-checks": "没有检查"
},
+ "run": "运行检查",
"navigator": {
"changes": "变更项",
"checks": "SQL 检查",
@@ -1219,7 +1220,7 @@
"rollout": {
"rollouts": "发布任务",
"bypass-stage-requirements": "绕过提醒",
- "task-execution-errors": "任务执行警告",
+ "task-execution-errors": "任务执行错误",
"stage": {
"self": "阶段 | 阶段",
"run-stage": "运行任务",
@@ -1519,8 +1520,7 @@
"create": "创建环境",
"reorder": "重新排序环境",
"successfully-updated-environment": "环境'{name}'更新成功",
- "production-environment": "生产环境",
- "statement-execution": {}
+ "production-environment": "生产环境"
},
"quick-start": {
"self": "新手任务",
@@ -1556,7 +1556,7 @@
},
"password-forget": {
"title": "忘记了您的密码?",
- "selfhost": "请联系的您的 Bytebase 管理员重置密码",
+ "selfhost": "请联系您的 Bytebase 管理员重置密码",
"cloud": "请登录 {link} 并重置密码",
"return-to-sign-in": "返回登录"
},
@@ -1882,8 +1882,8 @@
"self": "项目标签",
"description": "用键值标签组织项目(最多64个)"
},
- "confirm-archive-project": "Archiving \"{name}\" will make it read-only and hide it from active project lists. All issues, databases, and settings will be preserved. You can restore it later from the archived projects list.",
- "confirm-delete-project": "Deleting \"{name}\" will permanently remove the project and all associated data including issues, configurations, and history. All databases in this project will be moved to the default project. This action cannot be undone."
+ "confirm-archive-project": "归档「{name}」将使其变为只读并从活跃项目列表中隐藏。所有工单、数据库和设置将被保留。您可以稍后从已归档项目列表中恢复。",
+ "confirm-delete-project": "删除「{name}」将永久移除该项目及所有关联数据,包括工单、配置和历史记录。该项目中的所有数据库将被移至默认项目。此操作无法撤销。"
},
"members": {
"description": "项目成员角色决定了操作项目中的数据库和工单的权限。项目的所有者,工作空间管理员和 DBA 都具有项目所有的权限。",
@@ -1910,23 +1910,23 @@
"batch": {
"selected": "已选择 {count} 个项目 | 已选择 {count} 个项目",
"archive": {
- "title": "存档 {count} 项目?| 存档 {count} 项目?",
- "description": "这将存档所选项目。如有需要,您可以稍后恢复它们。",
+ "title": "归档 {count} 个项目?| 归档 {count} 个项目?",
+ "description": "这将归档所选项目。如有需要,您可以稍后恢复它们。",
"success": "成功归档 {count} 个项目 | 成功归档 {count} 个项目",
- "error": "无法存档项目"
+ "error": "无法归档项目"
},
"delete": {
"title": "删除 {count} 个项目?| 删除 {count} 个项目?",
"description": "这将永久删除所选项目,并将所有数据库移动到默认项目。",
- "warning": "此操作无法撤消。包括问题、配置和历史记录在内的所有项目数据将被永久删除。",
+ "warning": "此操作无法撤消。包括工单、配置和历史记录在内的所有项目数据将被永久删除。",
"success": "成功删除 {count} 个项目 | 成功删除 {count} 个项目",
"error": "无法删除项目"
},
- "projects-to-archive": "要存档的项目",
+ "projects-to-archive": "要归档的项目",
"projects-to-delete": "要删除的项目",
"resource-warning": {
"title": "项目与资源",
- "description": "以下项目包含数据库或未解决的问题:"
+ "description": "以下项目包含数据库或未解决的工单:"
}
}
},
@@ -2226,7 +2226,7 @@
"key-necessary": "需要指定 Key",
"value-necessary": "需要指定值",
"key-duplicated": "Key 重复了",
- "max-value-length-exceeded": "值长的度不能超过 {length} 字符"
+ "max-value-length-exceeded": "值的长度不能超过 {length} 字符"
},
"add-label": "添加标签"
},