Database structure of Lino Patrols

This document describes the database structure.

A tested document

This is a tested document. The following instructions are used for initialization:

>>> import lino
>>> lino.startup('lino_patrols.projects.patrols1.settings')
>>> from lino.api.doctest import *

>>> from lino.utils.diag import analyzer
>>> analyzer.show_db_overview()
...
25 plugins: lino, system, patrols, courses, contenttypes, gfks, printing, xl, cal, uploads, webforms, users, office, linod, checkdata, summaries, jinja, weasyprint, export_excel, memo, help, about, react, staticfiles, sessions.
30 models:
============================ ============================= ========= =======
 Name                         Default table                 #fields   #rows
---------------------------- ----------------------------- --------- -------
 cal.Calendar                 cal.Calendars                 6         1
 cal.EntryRepeater            cal.EntryRepeaterTable        17        0
 cal.Event                    cal.Events                    25        1296
 cal.EventPolicy              cal.EventPolicies             20        6
 cal.EventType                cal.EventTypes                24        3
 cal.Guest                    cal.Guests                    6         2016
 cal.GuestRole                cal.GuestRoles                5         2
 cal.RecurrentEvent           cal.RecurrentEvents           22        15
 cal.RemoteCalendar           cal.RemoteCalendars           7         0
 cal.Room                     cal.Rooms                     7         0
 cal.Subscription             cal.Subscriptions             4         0
 cal.Task                     cal.Tasks                     16        0
 checkdata.Message            checkdata.Messages            6         2
 contenttypes.ContentType     gfks.ContentTypes             3         30
 courses.Course               courses.Activities            30        14
 courses.Enrolment            courses.Enrolments            12        0
 courses.Line                 courses.Lines                 18        7
 courses.Slot                 courses.Slots                 5         2
 courses.Topic                courses.Topics                4         1
 linod.SystemTask             linod.SystemTasks             25        5
 memo.Mention                 memo.Mentions                 5         0
 sessions.Session             users.Sessions                3         3
 system.SiteConfig            system.SiteConfigs            10        1
 uploads.Upload               uploads.Uploads               12        13
 uploads.UploadType           uploads.UploadTypes           8         0
 uploads.Volume               uploads.Volumes               4         2
 users.Authority              users.Authorities             3         0
 users.User                   users.AllUsers                22        3
 webforms.ContactRequest      webforms.ContactRequests      12        0
 webforms.CreateUserRequest   webforms.CreateUserRequests   13        0
============================ ============================= ========= =======

The footer

This section is to verify #6896 (The footer renders memo commands using admin instead of publisher). The links in the footer worked in noi2, but not in patrols1. An anonymous user was faced with a sign-in dialog when they clicked them. The memo commands in the full_body_preview had been rendered using the admin front end and not using the publisher front end. That was because both plugins memo and publisher define a post_site_startup() method, memo uses it for setting self.ar to a BaseRequest with renderer=self.front_end.renderer, and publisher uses it for setting self.renderer = Renderer(self). The memo plugin now raises an exception “The memo plugin must come after {self.front_end}” when this situation occurs.

>>> dd.plugins.memo.front_end
lino.modlib.publisher

>>> p = publisher.SpecialPages.contact.get_object()

>>> ar = rt.login("robin", renderer=dd.plugins.memo.front_end.renderer, show_urls=True)
>>> ar.renderer
<lino.modlib.publisher.renderer.Renderer object at ...>
>>> ar.renderer.obj2url(ar, p)
'/p/contact'

>>> footer = publisher.SpecialPages.footer.get_object()

>>> ar = rt.login("robin", show_urls=True)
>>> ar.renderer
<lino.core.renderer.TextRenderer object at ...>
>>> s = beautiful_soup(footer.get_body_parsed(ar))
>>> print(s.find_all("a")[1])
<a href="/admin/#/api/publisher/Pages/22">Contact</a>

>>> ar = rt.login("robin", renderer=dd.plugins.memo.front_end.renderer, show_urls=True)
>>> ar.renderer
<lino.modlib.publisher.renderer.Renderer object at ...>
>>> s = beautiful_soup(footer.get_body_parsed(ar))
>>> print(s.find_all("a")[1])
<a href="/p/contact" style="text-decoration:none; white-space:nowrap;">Contact</a>

>>> s = beautiful_soup(footer.body_full_preview)
>>> print(s.find_all("a")[1])
<a href="/p/contact" style="text-decoration:none; white-space:nowrap;">Contact</a>