c78ffbcd18
assignments on the base schedule are shown in the pages for the schedule, read-only. This allows managing things like breaks and misc sessions separately from the regular WG sessions. Base schedules are not allowed to be the base of other base schedules (the hierarchy can only be one level deep) to simplify the mental model and the code. Add link for creating new schedules instead of relying on copying Empty-Schedule and change the meeting creation code to no longer create the special Empty-Schedule. Instead a "base" schedule is created and a first schedule with the name and permissions of the user creating the meeting, using "base" as base. Speed up a couple of the Secretariat/AD agenda views by adding prefetches. - Legacy-Id: 18355
26 lines
892 B
Python
26 lines
892 B
Python
# Generated by Django 2.0.13 on 2020-08-07 09:30
|
|
|
|
from django.db import migrations
|
|
import django.db.models.deletion
|
|
import ietf.utils.models
|
|
|
|
|
|
class Migration(migrations.Migration):
|
|
|
|
dependencies = [
|
|
('meeting', '0031_add_session_origin'),
|
|
]
|
|
|
|
operations = [
|
|
migrations.AddField(
|
|
model_name='schedule',
|
|
name='base',
|
|
field=ietf.utils.models.ForeignKey(blank=True, help_text='Sessions scheduled in the base show up in this schedule.', null=True, on_delete=django.db.models.deletion.SET_NULL, related_name='derivedschedule_set', to='meeting.Schedule'),
|
|
),
|
|
migrations.AlterField(
|
|
model_name='schedule',
|
|
name='origin',
|
|
field=ietf.utils.models.ForeignKey(blank=True, null=True, on_delete=django.db.models.deletion.SET_NULL, related_name='+', to='meeting.Schedule'),
|
|
),
|
|
]
|