ayanova/devdocs/todo.txt

@@ -12,15 +12,21 @@
 	new testing cases
 		case 3965 case sensitivity in data table filters and inconsistency
 			Filtering vs Searching is a useful concept to apply to this
-			tolowercase is not useful for almost any language other than english
-				actually, as long as the locale matches then it's fine
+			tolowercase is ok to use as long as the locale matches the entry language then it's fine
 				locale is determined by db default which is determined by server default
 				help docs (ours) link that should be added and page dedicated to locale issues:
-					https://www.postgresql.org/docs/current/locale.html
-				Need a tolowercase check in .net core, does it also follow the server setting?
+					
+			todo: Need a tolowercase check in .net core, does it also follow the server setting?
 					should I just allow postgres to do all tolower stuff by default? (probably)
-			citext is cited a lot for this kind of issue, it's a postgres module of some kind?
-			todo: add "Show All" query results to support info (or at least show lc_collate - Shows the collation order locale and show lc_ctype Shows the character classification and case conversion locale.)
+			todo: help docs specific page about db collation ("sorting") and case sensitivity etc
+				How AyaNova does case insensitive matching
+				How AyaNova does collation (db server specific)
+				link to postgres locale stuff here:https://www.postgresql.org/docs/current/locale.html
+			todo: make all "filter" queries use global case setting
+				this means picklist queries and datalist ("filtering") use global settings but search form ("Searching") does not
+			todo: keep the one setting for global that affects filtering only BUT, make sure it's translated to say "filter" not "search"			
+			todo: add locale settings of db server to log / support info ("show lc_collate" - Shows the collation order locale and "show lc_ctype" Shows the character classification and case conversion locale)
+
 
 	Schedule form
 	Dashboard / widgets