hacked around auto-increment primary key, so added note to README to come back to maybe fix this
This commit is contained in:
4
README
4
README
@@ -25,8 +25,6 @@ python3 main.py
|
|||||||
|
|
||||||
|
|
||||||
### TODO:
|
### TODO:
|
||||||
- need to save a book
|
|
||||||
- not sure about series/loan/subbook, etc.
|
|
||||||
- need to create all classes (green + button)
|
- need to create all classes (green + button)
|
||||||
- need to delete all classes (and watch for referential integrity)
|
- need to delete all classes (and watch for referential integrity)
|
||||||
- need to add 1 author to book, book to sub_book, series
|
- need to add 1 author to book, book to sub_book, series
|
||||||
@@ -42,3 +40,5 @@ python3 main.py
|
|||||||
### MAYBE:
|
### MAYBE:
|
||||||
when moving a book in a series (which is part of 2 series), do we pop-up
|
when moving a book in a series (which is part of 2 series), do we pop-up
|
||||||
offer to move parent/child series orders as well to match (think Thomas Covenant)
|
offer to move parent/child series orders as well to match (think Thomas Covenant)
|
||||||
|
|
||||||
|
try to "export" db from sqlalchemy to see what it is doing with sequences / primary key for owned table and maybe "new_id" not needed?
|
||||||
|
|||||||
Reference in New Issue
Block a user