View Single Post
Old 11-24-2022, 11:18 AM   #327
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
Originally Posted by ownedbycats View Post
Thanks. Is there technical reason it's excluded? I was wanting to compare it against a custom datetime column.

When I was developing the very first Tab in MCS, I intentionally excluded that column from the Scope of MCS, and nothing has changed in the intervening 7.5 years.



Your simple solution is to create a new datetime custom column, and use S&R to copy the unsupported datetime field you wish to it. Then, use MCS to compare that new column to another datetime column of your choosing. Afterwards, purge the data in, or delete entirely, that new custom column, and compress your Library's metadata.db.





DaltonST
DaltonST is offline   Reply With Quote