updating README to add more todos, clarify after some testing

README

@@ -29,7 +29,12 @@ python3 main.py
 	offer to move parent/child series orders as well to match (think Thomas Covenant)
 
 ### TODO: 
+	- need to trap failed sqls (e.g. delete a used foreign key - like a rating, should say gracefully alert you) - done for:
+		- rating CRUD
+		- book update, delete
+			-- I guess we could check for 'duplicate' book creation...
 	- consider created/modifed for all fields? but mostly are they set via ORM for new books?
+		* No, not being set...
 	- need to delete 1 sub_book from book
 		* swap the 'add sub book' for 'remove from parent book' button and then act on it (separate route, simple sql exec and route back to (no-longer) child book) 
 			(noting that deleting a child book already removes the book_sub_book_link)
@@ -37,7 +42,7 @@ python3 main.py
 		(remove all sub books from series too?)
 	- need to delete all classes (and watch for referential integrity)
 		* book (as long as no sub-books)... 
-			NOT tested how this goes with deleting book that is in a loan, or book that is in a series
+			-- dependency issue with series
 		- can delete:
 			author, publisher, series, condition, covertype, owned, rating, genre, loan,
 	- should deleting really just ask if want to mark it as SOLD?
@@ -54,6 +59,8 @@ python3 main.py
 	- view list of possible duplicate books by title
 	- consider which of the 'books maybe not valid' reports make sense still
 	  (can you even have an N/A publisher now for example, but the genre one is interesting)
-
+	- icons for on wish list, etc.?  (not sure I really want them, but if so)
+		- wishlist: search-dollar OR https://www.flaticon.com/free-icon/wishlist_868517
+		- save: https://www.flaticon.com/free-icon/sold_463255?term=sold&page=1&position=6&related_item_id=463255
 	
 	- with ORM: should I lazy load all books (ajax the 2nd->last pages in, or not use ORM, and do a quick db.execute()....)