devdocs/specs/core-picklist-autocomplete-template-system.txt

@@ -31,9 +31,12 @@ AUTOCOMPLETE
 				- has default view if not overriden that is generally good enough for anyone
 			- PickList Controller ROUTES
 				- GET PickList/List(AyaType, query)
-					- Uses cached view (fetches into cache if not fetched to keep cache small)
+					- Does NOT use cached view.
-						- Use best practice caching for this so can extend to other things that need caching like BizRoles
+						- after some research caches should only be used if:
-					- Based on cached view constructs a query with relevant columns only and containing search query in each column
+							- The data is very expensive in time to generate
+							- small, not likely to take up much memory
+						- There is a *lot* of fuckery involved with caches, basically it should not be used for anything I'm doing so far
+					- Based on saved template view constructs a query with relevant columns only and containing search query in each column
 						- Also handles tags properly	
 				- PUT PickList/Template (body AyaType, body viewJson)
 					- Update a view to use a new default

server/AyaNova/Controllers/PickListController.cs

@@ -40,6 +40,10 @@ namespace AyaNova.Api.Controllers
             serverState = apiServerState;
         }
 
+TODO: need a db schema table and objects to hold the picklist templates
+//while they may have an ID to make them easier to work with, they are fetched and stored by the object type only (which is a type of id and unique so maybe it's still id
+//but not an autonumber type id, have to check into that)
+
 
 
         /// <summary>