commented out code should be removed or reason given for why it is commented out / should be in the code long term.
I would add them as 1 combined index as I don't think you would ever be providing one without the other ----- also, what should the included columns be for the index?
Should there be a…
not sure if this would help --- but just a thought - passing in a whole table of the annotationtypeselections instead of doing 1 update/insert at a time and then doing a merge with the current…
sounds good. Just wanted to double check since this existed before your changes that removing it wasn't going to impact something else.
was this (ProcItem = CurrentItem.MyProcedure;) intended to be removed?
UsrID is the id of the PROMS user. Userid is the user id that created the annotation type.
can we either --- use something else like CreatedBy or add a comment in the SQL.
I would add them as 1 combined index as I don't think you would ever be providing one without the other ----- also, what should the included columns be for the index?
Must be missing something .... Not sure I understand why we are deleting items and reentering them ...... wouldn't we lose history on when they were originally put in if we do that?
this line is: cbGridAnnoType.DataSource = AnnotationTypeInfoList.Get().Clone();
2-4 lines below have:
cbGridAnnoType.DataSource = VEPROMS.CSLA.Library.AnnotationstypeSelections.Get(MyUserInf…
unless reason for keeping the commented out code (should be explained in the comments) --- commented out code shouldn't be checked in?
Now, this is a method with everything inside commented out --- if no code is to execute, should the method be removed?