Mobile: "on-conflict-user-mobile",
	}
	err = DB.Create(&u).Error
	AssertEqual(t, err, nil)

	u.Name = "on-conflict-user-name-2"
	u.Email = "on-conflict-user-email-2"
	u.Mobile = ""
	err = DB.Clauses(clause.OnConflict{UpdateAll: true}).Create(&u).Error
	AssertEqual(t, err, nil)

	var u2 OnConflictUser
	err = DB.Where("id = ?", u.ID).First(&u2).Error
	AssertEqual(t, err, nil)

// Package clause provides the clause interface and common clause implementations for GORM.
package clause

// Interface clause interface
type Interface interface {
	Name() string
	Build(Builder)
	MergeClause(*Clause)
}

// ClauseBuilder clause builder, allows to customize how to build clause
type ClauseBuilder func(Clause, Builder)

type Writer interface {
	WriteByte(byte) error
	WriteString(string) (int, error)
}

```Python
something(some_argument, some_keyword_argument="foo")
```

alors c'est un « callable ».

## Utiliser des classes comme dépendances { #classes-as-dependencies_1 }

Vous remarquerez que pour créer une instance d'une classe Python, vous utilisez la même syntaxe.

Par exemple :

```Python
class Cat:
    def __init__(self, name: str):
        self.name = name


fluffy = Cat(name="Mr Fluffy")
```

```

entonces es un "callable".

## Clases como dependencias { #classes-as-dependencies_1 }

Puedes notar que para crear una instance de una clase en Python, utilizas esa misma sintaxis.

Por ejemplo:

```Python
class Cat:
    def __init__(self, name: str):
        self.name = name


fluffy = Cat(name="Mr Fluffy")
```

En este caso, `fluffy` es una instance de la clase `Cat`.

- Use `OptionalEntity<T>` for nullable returns
- Plain classes (no extends/implements)

### Helper
- Stateless utility classes
- Access via `ComponentUtil.getXyzHelper()`
- Named with "Helper" suffix

### DBFlute Generated Code
```
opensearch/{index}/
├── bsentity/, bsbhv/    # Base classes (DO NOT EDIT)
├── exentity/, exbhv/    # Extended classes (customize here)

mvn license:format                    # Apply license headers
mvn verify                            # Generate coverage report
```

## Code Conventions

### Class Structure

- **Utility classes**: `abstract` class + `protected` constructor
- **Constants classes**: Same pattern

### Argument Validation

Use `AssertionUtil` at method entry:
- `AssertionUtil.assertArgumentNotNull("argName", value)`

або

```Python
something(some_argument, some_keyword_argument="foo")
```

тоді це «викликаємий».

## Класи як залежності { #classes-as-dependencies_1 }

Ви могли помітити, що для створення екземпляра класу Python ви використовуєте той самий синтаксис.

Наприклад:

```Python
class Cat:
    def __init__(self, name: str):
        self.name = name


fluffy = Cat(name="Mr Fluffy")
```

1. Read related source files and tests
2. Write implementation following existing patterns
3. Add comprehensive tests
4. Run `mvn formatter:format license:format test`
5. Update JavaDoc for changed/new classes

**Principles:**
- Avoid over-engineering - keep solutions simple
- Only expose necessary public APIs
- Validate parameters with `Objects.requireNonNull()`
- Provide detailed error messages with context

```

then it is a "callable".

## Classes as dependencies { #classes-as-dependencies_1 }

You might notice that to create an instance of a Python class, you use that same syntax.

For example:

```Python
class Cat:
    def __init__(self, name: str):
        self.name = name


fluffy = Cat(name="Mr Fluffy")
```

In this case, `fluffy` is an instance of the class `Cat`.

```Python
something(some_argument, some_keyword_argument="foo")
```

Então esse objeto é um "chamável".

## Classes como dependências { #classes-as-dependencies_1 }

Você deve ter percebido que para criar um instância de uma classe em Python, a mesma sintaxe é utilizada.

Por exemplo:

```Python
class Cat:
    def __init__(self, name: str):
        self.name = name


fluffy = Cat(name="Mr Fluffy")
```