Wednesday, January 25, 2017¶
A quick routine upgrade which required a snapshot & restore, but no explicit data migration.
I used the following a trick for checking whether the database needs migration or not:
Make a snapshot:
Update the code repositories:
dump2pyinto a temporary directory:
$ python manage.py dump2py -o t
$ python manage.py run snapshot/restore.py
I quickly fixed #1422 en passant (or at least one part of the request: the free_places column is now an IntegerField and therefore right-aligned)
Moving translations from one package to another¶
When you move some code from one package to another (e.g. from a to b) :
inv mmin both projects before starting
Move the code. Get it more or less running, but don’t worry for the test suite.
With your editor, manually copy the content of the
django.pofile of every language from project a and paste it to the end of its equivalent file in b. Do not copy the header fields.
inv mmagain in both projects
Preparing a demo on Thursday¶
Gerd and Mathieu will give a demo of Lino Welfare on Thursday. I did a last upgrade of the online demos.
The symbol used by
ActorItem.renderfor representing the button which opens a dashboard item in its own window is no longer 🗗 but ⍐. The problem with the former was that it is not yet supported on many browsers.
households module has a cool
feature: you can enter members by either (1) selecting an existing
client or (2) manually entering their names, birth date and sex. And
when you enter all four manual fields (first name, last name, birth
date and sex) for a member, then Lino automatically creates a client
for that member and links them.
This change caused an interesting failure in households. That was because household memberships automatically create human links when necessary, and new households are automatically populated from the children of the head of households and her or his partner.