New Crowdin updates (#768)

* Update source file create.md * New translations create.md (French) * New translations create.md (Spanish) * New translations create.md (Arabic) * New translations create.md (German) * New translations create.md (Italian) * New translations create.md (Japanese) * New translations create.md (Korean) * New translations create.md (Polish) * New translations create.md (Russian) * New translations create.md (Turkish) * New translations create.md (Chinese Simplified) * New translations create.md (Portuguese, Brazilian) * New translations create.md (Indonesian) * New translations create.md (Persian) * New translations create.md (Azerbaijani) * New translations create.md (Hindi) * New translations advanced_query.md (French) * New translations advanced_query.md (Spanish) * New translations advanced_query.md (Arabic) * New translations advanced_query.md (German) * New translations advanced_query.md (Italian) * New translations advanced_query.md (Japanese) * New translations advanced_query.md (Korean) * New translations advanced_query.md (Polish) * New translations advanced_query.md (Russian) * New translations advanced_query.md (Turkish) * New translations advanced_query.md (Chinese Simplified) * New translations advanced_query.md (Portuguese, Brazilian) * New translations advanced_query.md (Indonesian) * New translations advanced_query.md (Persian) * New translations advanced_query.md (Azerbaijani) * New translations advanced_query.md (Hindi) * Update source file advanced_query.md * New translations community.md (Russian) * New translations contribute.md (Russian) * New translations advanced_query.md (Russian) * New translations contribute.md (Russian) * New translations models.md (French) * New translations polymorphism.md (French) * New translations models.md (Spanish) * New translations polymorphism.md (Spanish) * New translations models.md (Arabic) * New translations polymorphism.md (Arabic) * New translations models.md (German) * New translations polymorphism.md (German) * New translations models.md (Italian) * New translations polymorphism.md (Italian) * New translations models.md (Japanese) * New translations polymorphism.md (Japanese) * New translations models.md (Korean) * New translations polymorphism.md (Korean) * New translations models.md (Polish) * New translations polymorphism.md (Polish) * New translations models.md (Russian) * New translations polymorphism.md (Russian) * New translations models.md (Turkish) * New translations polymorphism.md (Turkish) * New translations models.md (Chinese Simplified) * New translations polymorphism.md (Chinese Simplified) * New translations models.md (Portuguese, Brazilian) * New translations polymorphism.md (Portuguese, Brazilian) * New translations models.md (Indonesian) * New translations polymorphism.md (Indonesian) * New translations models.md (Persian) * New translations polymorphism.md (Persian) * New translations models.md (Azerbaijani) * New translations polymorphism.md (Azerbaijani) * New translations models.md (Hindi) * New translations polymorphism.md (Hindi) * Update source file models.md * Update source file polymorphism.md * New translations associations.md (French) * New translations has_one.md (French) * New translations associations.md (Spanish) * New translations has_one.md (Spanish) * New translations associations.md (Arabic) * New translations has_one.md (Arabic) * New translations associations.md (German) * New translations has_one.md (German) * New translations associations.md (Italian) * New translations has_one.md (Italian) * New translations associations.md (Japanese) * New translations has_one.md (Japanese) * New translations associations.md (Korean) * New translations has_one.md (Korean) * New translations associations.md (Polish) * New translations has_one.md (Polish) * New translations associations.md (Russian) * New translations has_one.md (Russian) * New translations associations.md (Turkish) * New translations has_one.md (Turkish) * New translations associations.md (Chinese Simplified) * New translations has_one.md (Chinese Simplified) * New translations associations.md (Portuguese, Brazilian) * New translations has_one.md (Portuguese, Brazilian) * New translations associations.md (Indonesian) * New translations has_one.md (Indonesian) * New translations associations.md (Persian) * New translations has_one.md (Persian) * New translations associations.md (Azerbaijani) * New translations has_one.md (Azerbaijani) * New translations associations.md (Hindi) * New translations has_one.md (Hindi) * Update source file associations.md * Update source file has_one.md
go-gorm · Jul 12, 2024 · d543ab6 · d543ab6
1 parent 42acd5e
commit d543ab6
Show file tree

Hide file tree

Showing 98 changed files with 113 additions and 112 deletions.
diff --git a/pages/ar_SA/docs/advanced_query.md b/pages/ar_SA/docs/advanced_query.md
@@ -358,7 +358,7 @@ result := db.Where("processed = ?", false).FindInBatches(&results, 100, func(tx
 
 ## Query Hooks
 
-GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the databas.
+GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the database.
 
 This hook is useful for post-query data manipulation or default value settings. For more detailed information and additional hook types, refer to [Hooks](hooks.html) in the GORM documentation.
 

diff --git a/pages/ar_SA/docs/associations.md b/pages/ar_SA/docs/associations.md
@@ -145,7 +145,7 @@ db.Select("Account").Delete(&users)
 ```
 
 {% note warn %}
-**NOTE:** It's important to note that associations will only be deleted if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
+**NOTE:** It's important to note that associations will be deleted only if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
 
 ```go
 // This will not work as intended

diff --git a/pages/ar_SA/docs/has_one.md b/pages/ar_SA/docs/has_one.md
@@ -68,7 +68,7 @@ You are able to change it with tag `references`, e.g:
 type User struct {
  gorm.Model
  Name string `gorm:"index"`
- CreditCard CreditCard `gorm:"foreignKey:UserName;references:name"`
+ CreditCard CreditCard `gorm:"foreignKey:UserName;references:Name"`
 }
 
 type CreditCard struct {

diff --git a/pages/ar_SA/docs/models.md b/pages/ar_SA/docs/models.md
@@ -176,7 +176,7 @@ type Blog struct {
 
 ### <span id="tags">Fields Tags</span>
 
-Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred.
+Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred. If multiple tags are used they should be separated by a semicolon (`;`). Characters that have special meaning to the parser can be escaped with a backslash (`\`) allowing them to be used as parameter values.
 
 | Tag Name | Description |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

diff --git a/pages/ar_SA/docs/polymorphism.md b/pages/ar_SA/docs/polymorphism.md
@@ -39,7 +39,7 @@ You can specify polymorphism properties separately using the following GORM tags
 type Dog struct {
  ID int
  Name string
- Toys Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
+ Toys []Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
 }
 
 type Toy struct {

diff --git a/pages/ar_SA/gen/create.md b/pages/ar_SA/gen/create.md
@@ -92,7 +92,7 @@ err := query.User.WithContext(ctx).Clauses(clause.OnConflict{
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET ***; SQL Server
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE ***; MySQL
 
-err := query.User.WithContext(ctx).Clauses(clause.OnConflict{Columns: []string{"Name", "Age"}}).Create(&user).Error
+err := query.User.WithContext(ctx).Clauses(clause.OnConflict{DoUpdates: clause.AssignmentColumns([]string{"name", "age"}),}).Create(&user).Error
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET "name"="excluded"."name"; SQL Server
 // INSERT INTO "users" *** ON CONFLICT ("id") DO UPDATE SET "name"="excluded"."name", "age"="excluded"."age"; PostgreSQL
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE `name`=VALUES(name),`age`=VALUES(age); MySQL

diff --git a/pages/az_AZ/docs/advanced_query.md b/pages/az_AZ/docs/advanced_query.md
@@ -358,7 +358,7 @@ result := db.Where("processed = ?", false).FindInBatches(&results, 100, func(tx
 
 ## Query Hooks
 
-GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the databas.
+GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the database.
 
 This hook is useful for post-query data manipulation or default value settings. For more detailed information and additional hook types, refer to [Hooks](hooks.html) in the GORM documentation.
 

diff --git a/pages/az_AZ/docs/associations.md b/pages/az_AZ/docs/associations.md
@@ -145,7 +145,7 @@ db.Select("Account").Delete(&users)
 ```
 
 {% note warn %}
-**NOTE:** It's important to note that associations will only be deleted if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
+**NOTE:** It's important to note that associations will be deleted only if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
 
 ```go
 // This will not work as intended

diff --git a/pages/az_AZ/docs/has_one.md b/pages/az_AZ/docs/has_one.md
@@ -68,7 +68,7 @@ You are able to change it with tag `references`, e.g:
 type User struct {
  gorm.Model
  Name string `gorm:"index"`
- CreditCard CreditCard `gorm:"foreignKey:UserName;references:name"`
+ CreditCard CreditCard `gorm:"foreignKey:UserName;references:Name"`
 }
 
 type CreditCard struct {

diff --git a/pages/az_AZ/docs/models.md b/pages/az_AZ/docs/models.md
@@ -172,7 +172,7 @@ type Blog struct {
 
 ### <span id="tags">Fields Tags</span>
 
-Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred.
+Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred. If multiple tags are used they should be separated by a semicolon (`;`). Characters that have special meaning to the parser can be escaped with a backslash (`\`) allowing them to be used as parameter values.
 
 | Tag Name | Description |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

diff --git a/pages/az_AZ/docs/polymorphism.md b/pages/az_AZ/docs/polymorphism.md
@@ -39,7 +39,7 @@ You can specify polymorphism properties separately using the following GORM tags
 type Dog struct {
  ID int
  Name string
- Toys Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
+ Toys []Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
 }
 
 type Toy struct {

diff --git a/pages/az_AZ/gen/create.md b/pages/az_AZ/gen/create.md
@@ -92,7 +92,7 @@ err := query.User.WithContext(ctx).Clauses(clause.OnConflict{
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET ***; SQL Server
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE ***; MySQL
 
-err := query.User.WithContext(ctx).Clauses(clause.OnConflict{Columns: []string{"Name", "Age"}}).Create(&user).Error
+err := query.User.WithContext(ctx).Clauses(clause.OnConflict{DoUpdates: clause.AssignmentColumns([]string{"name", "age"}),}).Create(&user).Error
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET "name"="excluded"."name"; SQL Server
 // INSERT INTO "users" *** ON CONFLICT ("id") DO UPDATE SET "name"="excluded"."name", "age"="excluded"."age"; PostgreSQL
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE `name`=VALUES(name),`age`=VALUES(age); MySQL

diff --git a/pages/de_DE/docs/advanced_query.md b/pages/de_DE/docs/advanced_query.md
@@ -358,7 +358,7 @@ result := db.Where("processed = ?", false).FindInBatches(&results, 100, func(tx
 
 ## Query Hooks
 
-GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the databas.
+GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the database.
 
 This hook is useful for post-query data manipulation or default value settings. For more detailed information and additional hook types, refer to [Hooks](hooks.html) in the GORM documentation.
 

diff --git a/pages/de_DE/docs/associations.md b/pages/de_DE/docs/associations.md
@@ -145,7 +145,7 @@ db.Select("Account").Delete(&users)
 ```
 
 {% note warn %}
-**NOTE:** It's important to note that associations will only be deleted if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
+**NOTE:** It's important to note that associations will be deleted only if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
 
 ```go
 // This will not work as intended

diff --git a/pages/de_DE/docs/has_one.md b/pages/de_DE/docs/has_one.md
@@ -68,7 +68,7 @@ You are able to change it with tag `references`, e.g:
 type User struct {
  gorm.Model
  Name string `gorm:"index"`
- CreditCard CreditCard `gorm:"foreignKey:UserName;references:name"`
+ CreditCard CreditCard `gorm:"foreignKey:UserName;references:Name"`
 }
 
 type CreditCard struct {

diff --git a/pages/de_DE/docs/models.md b/pages/de_DE/docs/models.md
@@ -172,7 +172,7 @@ type Blog struct {
 
 ### <span id="tags">Fields Tags</span>
 
-Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred.
+Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred. If multiple tags are used they should be separated by a semicolon (`;`). Characters that have special meaning to the parser can be escaped with a backslash (`\`) allowing them to be used as parameter values.
 
 | Tag Name | Description |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

diff --git a/pages/de_DE/docs/polymorphism.md b/pages/de_DE/docs/polymorphism.md
@@ -39,7 +39,7 @@ You can specify polymorphism properties separately using the following GORM tags
 type Dog struct {
  ID int
  Name string
- Toys Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
+ Toys []Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
 }
 
 type Toy struct {

diff --git a/pages/de_DE/gen/create.md b/pages/de_DE/gen/create.md
@@ -92,7 +92,7 @@ err := query.User.WithContext(ctx).Clauses(clause.OnConflict{
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET ***; SQL Server
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE ***; MySQL
 
-err := query.User.WithContext(ctx).Clauses(clause.OnConflict{Columns: []string{"Name", "Age"}}).Create(&user).Error
+err := query.User.WithContext(ctx).Clauses(clause.OnConflict{DoUpdates: clause.AssignmentColumns([]string{"name", "age"}),}).Create(&user).Error
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET "name"="excluded"."name"; SQL Server
 // INSERT INTO "users" *** ON CONFLICT ("id") DO UPDATE SET "name"="excluded"."name", "age"="excluded"."age"; PostgreSQL
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE `name`=VALUES(name),`age`=VALUES(age); MySQL

diff --git a/pages/es_ES/docs/advanced_query.md b/pages/es_ES/docs/advanced_query.md
@@ -358,7 +358,7 @@ result := db.Where("processed = ?", false).FindInBatches(&results, 100, func(tx
 
 ## Consultas Hooks
 
-GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the databas.
+GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the database.
 
 This hook is useful for post-query data manipulation or default value settings. For more detailed information and additional hook types, refer to [Hooks](hooks.html) in the GORM documentation.
 

diff --git a/pages/es_ES/docs/associations.md b/pages/es_ES/docs/associations.md
@@ -145,7 +145,7 @@ db.Select("Account").Delete(&users)
 ```
 
 {% note warn %}
-**NOTE:** It's important to note that associations will only be deleted if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
+**NOTE:** It's important to note that associations will be deleted only if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
 
 ```go
 // This will not work as intended

diff --git a/pages/es_ES/docs/has_one.md b/pages/es_ES/docs/has_one.md
@@ -68,7 +68,7 @@ You are able to change it with tag `references`, e.g:
 type User struct {
  gorm.Model
  Name string `gorm:"index"`
- CreditCard CreditCard `gorm:"foreignKey:UserName;references:name"`
+ CreditCard CreditCard `gorm:"foreignKey:UserName;references:Name"`
 }
 
 type CreditCard struct {

diff --git a/pages/es_ES/docs/models.md b/pages/es_ES/docs/models.md
@@ -172,7 +172,7 @@ type Blog struct {
 
 ### <span id="tags">Fields Tags</span>
 
-Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred.
+Tags are optional to use when declaring models, GORM supports the following tags: Tags are case insensitive, however `camelCase` is preferred. If multiple tags are used they should be separated by a semicolon (`;`). Characters that have special meaning to the parser can be escaped with a backslash (`\`) allowing them to be used as parameter values.
 
 | Tag Name | Description |
 | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

diff --git a/pages/es_ES/docs/polymorphism.md b/pages/es_ES/docs/polymorphism.md
@@ -39,7 +39,7 @@ You can specify polymorphism properties separately using the following GORM tags
 type Dog struct {
  ID int
  Name string
- Toys Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
+ Toys []Toy `gorm:"polymorphicType:Kind;polymorphicId:OwnerID;polymorphicValue:master"`
 }
 
 type Toy struct {

diff --git a/pages/es_ES/gen/create.md b/pages/es_ES/gen/create.md
@@ -92,7 +92,7 @@ err := query.User.WithContext(ctx).Clauses(clause.OnConflict{
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET ***; SQL Server
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE ***; MySQL
 
-err := query.User.WithContext(ctx).Clauses(clause.OnConflict{Columns: []string{"Name", "Age"}}).Create(&user).Error
+err := query.User.WithContext(ctx).Clauses(clause.OnConflict{DoUpdates: clause.AssignmentColumns([]string{"name", "age"}),}).Create(&user).Error
 // MERGE INTO "users" USING *** WHEN NOT MATCHED THEN INSERT *** WHEN MATCHED THEN UPDATE SET "name"="excluded"."name"; SQL Server
 // INSERT INTO "users" *** ON CONFLICT ("id") DO UPDATE SET "name"="excluded"."name", "age"="excluded"."age"; PostgreSQL
 // INSERT INTO `users` *** ON DUPLICATE KEY UPDATE `name`=VALUES(name),`age`=VALUES(age); MySQL

diff --git a/pages/fa_IR/docs/advanced_query.md b/pages/fa_IR/docs/advanced_query.md
@@ -356,7 +356,7 @@ result := db.Where("processed = ?", false).FindInBatches(&results, 100, func(tx
 
 ## Query Hooks
 
-GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the databas.
+GORM offers the ability to use hooks, such as `AfterFind`, which are triggered during the lifecycle of a query. These hooks allow for custom logic to be executed at specific points, such as after a record has been retrieved from the database.
 
 This hook is useful for post-query data manipulation or default value settings. For more detailed information and additional hook types, refer to [Hooks](hooks.html) in the GORM documentation.
 

diff --git a/pages/fa_IR/docs/associations.md b/pages/fa_IR/docs/associations.md
@@ -145,7 +145,7 @@ db.Select("Account").Delete(&users)
 ```
 
 {% note warn %}
-**NOTE:** It's important to note that associations will only be deleted if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
+**NOTE:** It's important to note that associations will be deleted only if the primary key of the deleting record is not zero. GORM uses these primary keys as conditions to delete the selected associations.
 
 ```go
 // This will not work as intended

diff --git a/pages/fa_IR/docs/has_one.md b/pages/fa_IR/docs/has_one.md
@@ -68,7 +68,7 @@ You are able to change it with tag `references`, e.g:
 type User struct {
  gorm.Model
  Name string `gorm:"index"`
- CreditCard CreditCard `gorm:"foreignKey:UserName;references:name"`
+ CreditCard CreditCard `gorm:"foreignKey:UserName;references:Name"`
 }
 
 type CreditCard struct {