[BUG] Manager defined in migration is not the clickhouse manager

[mhaVC]

Describe the bug
The migration for a new clickhouse model defines the objects manager as the default django manager rather than the ClickhouseManager used in the base ClickhouseModel class.
Accessing the manager in code does return the correct manager ie:

>> DummyModel.objects.__class__
clickhouse_backend.models.base.ClickhouseManager

To Reproduce
The model class:

class DummyModel(models.ClickhouseModel):
    url = models.StringField()

The migration:

# Generated by Django 5.1.2 on 2025-01-30 16:47

import clickhouse_backend.models
import django.db.models.manager
from django.db import migrations, models


class Migration(migrations.Migration):

    dependencies = [
        ("dummy_app", "0001_initial_migration"),
    ]

    operations = [
        migrations.CreateModel(
            name="DummyModel",
            fields=[
                (
                    "id",
                    models.AutoField(
                        auto_created=True,
                        primary_key=True,
                        serialize=False,
                        verbose_name="ID",
                    ),
                ),
                ("url", clickhouse_backend.models.StringField()),
            ],
            options={
                "abstract": False,
                "base_manager_name": "_overwrite_base_manager",
            },
            managers=[
                ("objects", django.db.models.manager.Manager()),
                ("_overwrite_base_manager", django.db.models.manager.Manager()),
            ],
        ),
    ]

Expected behavior
I'd have expected the managers definition in the migration to use the ClickhouseManager class.

Versions

• ClickHouse server version. Version can be obtained by running SELECT version() query.
  • 24.8
• Python version.
  • 3.10.14
• Clickhouse-driver version.
  • 0.2.9
• Django version.
  • 5.1.2
• Django clickhouse backend version.
  • 1.3.1

[mhaVC]

Is this behavior because django doesn't utilize custom managers in migrations?
Apologies if that is the case and I misunderstood this behavior as a bug