devdocs/specs/core-tags.txt

@@ -89,33 +89,4 @@ TAG GROUP DEPRECATED 2018-12-05
                 In this way the filters are always dynamically linked to the tags in the group and reflect the most recent changes to the group
                 tl/dr: don't store the tag id's from a group in the filter, store the group id separately and build the list on query
 
-                
+ 
-DEPRECATED 2018-12-05 SCHEMA
-This is outdated, going with an array in table solution instead, much better than this concept
-=-=-=-
-            4 tables:
-
-            TAGS
-                - name text not null lowercase only
-                - id bigserial
-                - OwnerId
-            
-            TAGMAP
-                - ObjectId
-                - ObjectType
-                - TagId
-
-            TAGGROUP
-                - name text not null lowercase only
-                - id bigserial
-                - OwnerId
-
-            TAGGROUPMAP
-                - TagGroupId   
-                - TagId   
-                
-            INDEXES
-                - Initial index is on the name of the tag as that will be searched for??
-                - After some research I think it's best to just make it, populate it with a great deal of test data and then test query it and see what indexes give the best performance
-                
-

devdocs/todo.txt

@@ -39,6 +39,7 @@ Do the stuff in the Client todo first then back to the server as required.
 
 DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER
 
+###*** BEFORE NEXT UPDATE TO DEVOPS SERVER:::::::
 TODO: Make it fucking easier to test deploy and erase db and fetch key and all that shit
 	- I would like to deploy, bring it up and then from a simple command from the api explorer trigger all the above
 	- OR, ding ding ding ding...FUCKING CODE THE CLIENT SIDE FOR OPS SHIT LIKE FETCHING KEY, ERASING DB ETC!!!!

server/AyaNova/Controllers/AttachmentController.cs

@@ -186,8 +186,8 @@ namespace AyaNova.Api.Controllers
                 if (!badRequest)
                 {
                     //check if object exists
-                    //Updated code: this used to check if the ownerId was -1 to see if it didn't exist, but since ownerId zapped this seems like the next best way to do it
+                    //Updated code: this used to check if the o wnerId was -1 to see if it didn't exist, but since ow nerId zapped this seems like the next best way to do it
-                    //Not sure at all what the ownerid check was doing before that verified it's existance, the code is long gone now and I can't be arsed to look it up in the repo history                   
+                    //Not sure at all what the ow nerid check was doing before that verified it's existance, the code is long gone now and I can't be arsed to look it up in the repo history                   
                     //If the tests pass then it's fine :)                   
                     if (!BizObjectExistsInDatabase.Exists(attachToObject))
                     {

server/AyaNova/Controllers/ImportAyaNova7Controller.cs

@@ -264,7 +264,7 @@ namespace AyaNova.Api.Controllers
             OpsJob j = new OpsJob();
             j.Name = $"Import AyaNova7 data (import file \"{filename}\"";
             j.JobType = JobType.ImportV7Data;
-            j.OwnerId = UserIdFromContext.Id(HttpContext.Items);
+            //j.O wnerId = UserIdFromContext.Id(HttpContext.Items);
             j.JobInfo = jobInfo.ToString();
             JobsBiz.AddJob(j, ct);
             return Accepted(new { JobId = j.GId });//202 accepted

server/AyaNova/models/OpsJob.cs

@@ -19,8 +19,8 @@ namespace AyaNova.Models
         public DateTime Created { get; set; }
         public uint ConcurrencyToken { get; set; }
 
-        [Required]
+        // [Required]
-        public long OwnerId { get; set; }
+        // public long O wnerId { get; set; }
         [Required]
         public string Name { get; set; }
 
@@ -43,7 +43,7 @@ namespace AyaNova.Models
         public OpsJob(){
             GId=new Guid();
             Created=DateTime.UtcNow;
-            OwnerId=1;
+          //  O wnerId=1;
             Name="new job";
             Exclusive=false;
             StartAfter=Created;