- Rename calendar_app → scheduling (integration app for django-scheduler) - Move schedule_patch.py → scheduling/patch.py with improved logging - Create scheduling.notifications system for django-scheduler events - Add scheduling.rules for django-rules integration - Remove unused calendar_app models and API (not registered in urls) - Remove backend/api/v1/calendar/ (dead code) - Remove old tests for calendar_app - Add comprehensive documentation in scheduling/README.md - Update settings.py: calendar_app.apps.CalendarAppConfig → scheduling.apps.SchedulingConfig - Clean api/apps.py: remove schedule_patch import (now in scheduling.apps) The scheduling app provides: - Patches for django-scheduler bugs (byweekday fix) - Notification system for calendar events - Access rules via django-rules - Auto-applies on Django startup Closes integration of django-scheduler for EUSRR calendar system.
35 lines
1.3 KiB
Python
35 lines
1.3 KiB
Python
# Generated by Django on 2026-03-10
|
||
|
||
from django.db import migrations
|
||
|
||
|
||
class Migration(migrations.Migration):
|
||
"""
|
||
Удаление старых таблиц calendar_app после миграции на django-scheduler.
|
||
|
||
ВАЖНО: Перед применением этой миграции убедитесь, что:
|
||
1. Все данные мигрированы в django-scheduler (таблицы schedule_*)
|
||
2. Приложение schedule работает корректно
|
||
3. Уведомления настроены в scheduling.notifications
|
||
4. Есть резервная копия БД
|
||
"""
|
||
|
||
dependencies = [
|
||
('calendar_app', '0013_migrate_to_django_scheduler'),
|
||
]
|
||
|
||
operations = [
|
||
# Удаляем таблицы calendar_app
|
||
migrations.RunSQL(
|
||
sql=[
|
||
"DROP TABLE IF EXISTS calendar_app_calendarevent CASCADE;",
|
||
"DROP TABLE IF EXISTS calendar_app_calendarsubscription CASCADE;",
|
||
"DROP TABLE IF EXISTS calendar_app_calendar CASCADE;",
|
||
],
|
||
reverse_sql=[
|
||
# Откат невозможен - данные удалены
|
||
# Восстанавливать нужно из бэкапа
|
||
],
|
||
),
|
||
]
|