queryConds = append(queryConds, clause.IN{Column: column, Values: values})

				if db.AddError(tx.Clauses(clause.Where{Exprs: queryConds}).Delete(modelValue).Error) != nil {
					return
				}
			}
		}

	}
}

func Delete(config *Config) func(db *gorm.DB) {
	supportReturning := utils.Contains(config.DeleteClauses, "RETURNING")

	return func(db *gorm.DB) {
		if db.Error != nil {

labels.popular_word_word_enabled=Popular Word Response
labels.supported_search_web=Web
labels.supported_search_none=Unavailable
labels.purge_search_log_day=Delete old search logs
labels.purge_job_log_day=Delete old job logs
labels.purge_user_info_day=Delete old user logs
labels.purge_by_bots=Bot names to delete logs
labels.log_level=Log Level
labels.csv_file_encoding=CSV File Encoding
labels.notification_to=Notification Mail

		return
	}

	users := []*User{
		GetUser("delete-returning-1", Config{}),
		GetUser("delete-returning-2", Config{}),
		GetUser("delete-returning-3", Config{}),
	}
	DB.Create(&users)

	var results []User
	DB.Where("name IN ?", []string{users[0].Name, users[1].Name}).Clauses(clause.Returning{}).Delete(&results)
	if len(results) != 2 {
		t.Errorf("failed to return delete data, got %v", results)
	}

	var count int64

```
mc replicate edit alias/bucket --id xyz.id --replicate "delete,delete-marker"
```

To re-enable replica metadata modification syncing,

```
mc replicate edit alias/bucket --id xyz.id --replicate "delete,delete-marker,replica-metadata-sync"
```

## MinIO Extension

### Replicating Deletes

 * <li>{@link #delete(String)} - Delete a suggest item by ID.</li>
 * <li>{@link #deleteByQuery(String)} - Delete suggest items by query string.</li>
 * <li>{@link #deleteByQuery(QueryBuilder)} - Delete suggest items by query builder.</li>
 * <li>{@link #deleteAll()} - Delete all suggest items.</li>
 * <li>{@link #deleteDocumentWords()} - Delete document words.</li>

case of versioned deletes a.k.a permanent delete of a version by doing a `mc rm --version-id` on a object, replication implementation marks a object version permanently deleted as `PENDING` purge and deletes the version from source after syncing to the target and ensuring target version is deleted. The delete marker being deleted or object version being deleted will still be visible on listing with `mc ls --versions` until the sync is completed. Objects marked as deleted will not be accessible via `GET`...

To permanently delete an object you need to specify the version you want to delete, only the user with appropriate permissions can permanently delete a version.  As shown below DELETE request called with a specific version id permanently deletes an object from a bucket. Delete marker is not added for DELETE requests with version id.

	}

	// Delete
	DB.Model(&blog).Association("Tags").Delete(tag5)
	var tags3 []Tag
	DB.Model(&blog).Association("Tags").Find(&tags3)
	if !compareTags(tags3, []string{"tag6"}) {
		t.Fatalf("Should find 1 tags after Delete")
	}

	if DB.Model(&blog).Association("Tags").Count() != 1 {
		t.Fatalf("Blog should has three tags after Delete")
	}

    /**
     * Deletes a suggestion from the specified index.
     *
     * @param client   the client to use for the operation
     * @param settings the settings to use for the operation
     * @param index    the name of the index from which to delete the suggestion
     * @param id       the ID of the suggestion to delete
     * @return a result object containing the outcome of the delete operation

	<target name="install.jars">
		<mkdir dir="${target.dir}" />
		<delete dir="${webinf.dir}/lib" />
		<mkdir dir="${webinf.dir}/lib" />
		<delete dir="${crawler.dir}/lib" />
		<mkdir dir="${crawler.dir}/lib" />
		<delete dir="${suggest.dir}/lib" />
		<mkdir dir="${suggest.dir}/lib" />
		<delete dir="${thumbnail.dir}/lib" />
		<mkdir dir="${thumbnail.dir}/lib" />
		<!-- annotation-api -->