ddp/books
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refined notes around series and validation logic

Browse Source
This commit is contained in:
Damien De Paoli
2020-12-30 23:40:52 +11:00
parent 244367af2a
commit 9571c45def
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README
View File

@@ -30,10 +30,11 @@ python3 main.py
### TODO: ### TODO:
- need to trap failed sqls (e.g. delete a used foreign key - like a rating, should say gracefully alert you) - done for: - need to trap failed sqls (e.g. delete a used foreign key - like a rating, should say gracefully alert you) - done for:
- condition, covertype, genre, owned, rating: CRUD done - condition, covertype, genre, owned, rating, series: CRUD done
- book update, delete - book update, delete
-- I guess we could check for 'duplicate' book creation... -- I guess we could check for 'duplicate' book creation...
- NEXT: series (see BUGs), author, publisher ALSO series delete has different order of button and form.validate(), needed to work...
MUST use this when we have a validator that is fancier than not empty (year_published in book and num_books in series SO FAR)
- consider created/modifed for all fields? but mostly are they set via ORM for new books? - consider created/modifed for all fields? but mostly are they set via ORM for new books?
* No, not being set... * No, not being set...
- need to delete 1 sub_book from book - need to delete 1 sub_book from book