expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-02-25 13:45:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Django version documn

Browse Source
This commit is contained in:
Philip Sargent
2023-02-11 23:04:08 +00:00
parent 069609e814
commit 678326aae3
6 changed files with 7 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
handbook/troggle/trog2030.html
View File

@@ -76,12 +76,13 @@ Documentation and a working list of on-going programming projects is the key to
useful week's work, e.g. extracting the parsed logbooks to use shelve() storage throughout instead of SQL. The next time someone like Radost comes
along during the next 5 years we want to be able to use them effectively.
</div>
<p>[Decrufting and refactoring has been continuous since 2020. The ExpeditionDay class was refactored away and many unused properties of classes have been removed. DB query optimisation is only just beginning in 2023 though.]
<h3>Option Zero.1</h2>
<div style="color:blue">
<p>We should probably review and revise all the over-complex templates, originally written in 2006, which do serious amounts of database querying,
and linked object sub-querying, within the template code. This is a nightmare to maintain and debug, e.g. see
the note at the bottom of <a href="/personexpedition/Wookey/1999">Wookey 1999 trips</a>.
and linked object sub-querying, within the template code. This is a nightmare to maintain and debug. <!--e.g. see
the note at the bottom of <a href="/personexpedition/Wookey/1999">Wookey 1999 trips</a> - this fixed itself after de-crufting elsewhere -->
<p>A possible goal would be to create all the data that will be displayed in a page as dictionaries - generated by obviously simple python, with
some Django query optimisations if necessary - which are then handed as 'context' to the Django page template (those files in <var>