## Guia oficial { #official-guide }

O Pydantic tem um [Guia de Migração](https://docs.pydantic.dev/latest/migration/) oficial do v1 para o v2.

Ele também inclui o que mudou, como as validações agora são mais corretas e rigorosas, possíveis ressalvas, etc.

Você pode lê-lo para entender melhor o que mudou.

## Testes { #tests }

## Офіційний посібник { #official-guide }

У Pydantic є офіційний [Посібник з міграції](https://docs.pydantic.dev/latest/migration/) з v1 на v2.

Там описано, що змінилося, як перевірки тепер стали коректнішими та суворішими, можливі застереження тощо.

Прочитайте його, щоб краще зрозуміти зміни.

## Тести { #tests }

## Официальное руководство { #official-guide }

У Pydantic есть официальное [руководство по миграции](https://docs.pydantic.dev/latest/migration/) с v1 на v2.

Там также описано, что изменилось, как валидации стали более корректными и строгими, возможные нюансы и т.д.

Прочитайте его, чтобы лучше понять, что изменилось.

## Тесты { #tests }

    }

    @Test
    public void test_normalizeCanonicalUrl_withCustomSchemeRelative() throws Exception {
        final FessXpathTransformer transformer = new FessXpathTransformer();
        // URI→URL migration: java.net.URL rejects unknown schemes like javascript:
        final String value = transformer.normalizeCanonicalUrl("http://example.com/", "javascript:void(0)");

Ici, nous créons les tables lors d'un événement de démarrage de l'application.

En production, vous utiliseriez probablement un script de migration qui s'exécute avant de démarrer votre application. 🤓

/// tip | Astuce

SQLModel aura des utilitaires de migration enveloppant Alembic, mais pour l'instant, vous pouvez utiliser [Alembic](https://alembic.sqlalchemy.org/en/latest/) directement.

///

        location at `ai_edge_litert.interpreter`, as the API
        `tf.lite.Interpreter` will be deleted in TF 2.20. See the
        [migration guide](https://ai.google.dev/edge/litert/migration) for
        details.

### Known Caveats

### Major Features and Improvements

*  `tf.lite`
    * `tfl.Cast` op is now supporting `bfloat16` in runtime kernel.

		Name                string    `gorm:"size:256"`
		Salary              float64   `gorm:"precision:3"`
		Birthday            time.Time `gorm:"precision:3"`
		NameIgnoreMigration string    `gorm:"size:128;-:migration"`
	}

	if err := DB.Table("user_migrate_columns").AutoMigrate(&UserMigrateColumn3{}); err != nil {
		t.Fatalf("failed to auto migrate, got error: %v", err)
	}

Elbette bazı durumlarda ön adımları birden fazla kez çalıştırmak sorun değildir; bu durumda yönetmesi çok daha kolay olur.

/// tip | İpucu

### Step 1: Ensure Elasticsearch minimum requirements are met

MinIO requires a 5.x series version of Elasticsearch. This is the latest major release series. Elasticsearch provides version upgrade migration guidelines [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html).

### Step 2: Add Elasticsearch endpoint to MinIO

kube-aws, kubeadm etc) for specific advice.

1.6 encourages etcd3, and switching from etcd2 to etcd3 involves a full
migration of data between different storage engines.  You must stop the API
from writing to etcd during an etcd2 -> etcd3 migration.  HA installations cannot
be migrated at the current time using the official Kubernetes procedure.