Files
Django_kube/django_code/apps/telegram_communication/migrations/0001_initial.py
T
pi-ux-ceandClaude Sonnet 4.6 b4545d6c99
Gitea Actions Demo / Explore-Gitea-Actions (push) Successful in 3s
Add telegram_communication app with dedicated DB routing
- Register TelegramCommunicationConfig in INSTALLED_APPS and add telegram_db to DATABASES
- Define TelegramData model mapped to the messages table
- Fix allow_migrate in ProjectDatabaseRouter: redirect and telegram entries were returning the DB name string (always truthy) instead of a boolean comparison, causing their migrations to bleed into every database
- Add telegram routing to db_for_read, db_for_write, allow_relation, and allow_migrate

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-30 13:20:40 +01:00

29 lines
954 B
Python

# Generated by Django 4.2.30 on 2026-06-30 12:13
from django.db import migrations, models
class Migration(migrations.Migration):
initial = True
dependencies = [
]
operations = [
migrations.CreateModel(
name='TelegramData',
fields=[
('id', models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')),
('message_id', models.IntegerField(max_length=100, null=True)),
('chat_id', models.IntegerField(max_length=100, null=True)),
('description', models.CharField(max_length=100, null=True)),
('creation_date', models.DateField(blank=True, null=True, verbose_name='Published')),
('expiration_date', models.DateField(blank=True, null=True, verbose_name='Published')),
],
options={
'db_table': 'messages',
},
),
]