From 73662fab87cc20bd469c1dfc4b4bee9de0ca62d4 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 12 Mar 2020 14:22:06 +0000 Subject: [PATCH] --- .../specs/core-picklist-autocomplete-template-system.txt | 9 ++++++--- server/AyaNova/Controllers/PickListController.cs | 4 ++++ 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/devdocs/specs/core-picklist-autocomplete-template-system.txt b/devdocs/specs/core-picklist-autocomplete-template-system.txt index 70aae0e3..7978ac79 100644 --- a/devdocs/specs/core-picklist-autocomplete-template-system.txt +++ b/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) - - Use best practice caching for this so can extend to other things that need caching like BizRoles - - Based on cached view constructs a query with relevant columns only and containing search query in each column + - Does NOT use cached view. + - after some research caches should only be used if: + - 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 diff --git a/server/AyaNova/Controllers/PickListController.cs b/server/AyaNova/Controllers/PickListController.cs index d97af030..29a78208 100644 --- a/server/AyaNova/Controllers/PickListController.cs +++ b/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) + ///