remove delete/db sections, they are done and fixed submit/delete button ordering

README

@@ -27,14 +27,10 @@ python3 main.py
 ### MAYBE:
 	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)
+### Remember:
+	MUST use form.errors when we have a validator that is fancier than not empty (year_published in book and num_books in series SO FAR)
 
 ### TODO: 
-	- 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, series: CRUD done
-		- book update, delete
-			-- I guess we could check for 'duplicate' book creation...
-		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?
 		* No, not being set...
 	- need to delete 1 sub_book from book
@@ -42,11 +38,6 @@ python3 main.py
 			(noting that deleting a child book already removes the book_sub_book_link)
 	- when remove a Parent book from a series, what do we do?
 		(remove all sub books from series too?)
-	- need to delete all classes (and watch for referential integrity)
-		* book (as long as no sub-books)... 
-			-- 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?
 	- need to add books to loan (on loan page, and via a book search?)
 	- need to delete book from loan