remove publisher* from main.py, for now remove ORM complexities for sub_books in books, just do it by hand and cleaned up a few debugs, comments

This commit is contained in:
2020-11-15 12:22:41 +11:00
parent 29f8189c97
commit c675786852
2 changed files with 16 additions and 21 deletions

9
README
View File

@@ -19,6 +19,11 @@ python3 main.py
### TODO:
- fix up lame book linkages to tabels that are so not 3nf, *_LST tables, etc.
- ORM:
- saving a book with the ORM is probably the last oddity... probably time to try it (in a sense, the book edit page is the only time we change things, maybe we mess with that book-query as its too slow, and for book edit, if we don't allow editing items like author/publisher, then may only need to set the objects we want to change... I'm sort of curious can you save a book table based on id, without saging its author table, seems that should be okay, but how do I save both, just create 2 objects and do it, but what if the ORM has auto-connected bunches of stuff, how do I update the connected stuff.... MAYBE, I need to get say loan or something first, then try all this? (make a pop-up for stuff like loans, but what about series or sub-book editing????)
- consider getting rest of Book class connected, e.g. series, loan, etc.
- see if we can break this out of main.py -- can't recall what was circular about this, but at least the wtf bits seem to be able to be moved out, so why not do that
- get main.html to be some sort of include so that other htmls, can be clicked on / use back button, reload, etc. and it all works, but the whoel thing feels like a discrete app
### MAYBE, I should make this a self-contained docker instance, then its a copy of the DB and anything I break will be fixable
### next step is to rename genre_lst to genre, and maybe do similar to all _lst tables... then add genre.py in and get it to work