Help us understand your request (check below):
Describe what you're trying to do
#406; I'm trying to cache enough information to build /guid/ pages to flat.
I need to cache whatever we want to display. (The actual data are stored elsewhere, this is just for the cache.)
I currently have entered usename and date, and last username and date. I run some lookups to (possibly imperfectly) translate those into agents for display on /guid/ pages.
Enteredby should never change, the costs to caching more of it would be mostly in terms of storage and long-term growth ability. (There are a finite number of things I can cache.)
I question the value of "last edited" as a single term to anyone; there's a full history available to "us" on demand, and I think any one edit can only make sense in that context.
I'm not sure why the public needs to know who entered a record, and that's basically meaningless without the full edit history anyway. (I can create a nearly-blank record, then someone else can change everything except the internal identifier.)
My inclination is to remove these data from the UI altogether, and just leave a "click for entered and edited" option for "us."
I hope this isn't controversial and can be resolved quickly and easily, but adding to AWG agenda Just In Case.
Please review the Arctos Code of Conduct to ensure respectful communication, and see https://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html for more information about submitting and managing Issues.
Help us understand your request (check below):
Describe what you're trying to do
#406; I'm trying to cache enough information to build /guid/ pages to flat.
I need to cache whatever we want to display. (The actual data are stored elsewhere, this is just for the cache.)
I currently have entered usename and date, and last username and date. I run some lookups to (possibly imperfectly) translate those into agents for display on /guid/ pages.
Enteredby should never change, the costs to caching more of it would be mostly in terms of storage and long-term growth ability. (There are a finite number of things I can cache.)
I question the value of "last edited" as a single term to anyone; there's a full history available to "us" on demand, and I think any one edit can only make sense in that context.
I'm not sure why the public needs to know who entered a record, and that's basically meaningless without the full edit history anyway. (I can create a nearly-blank record, then someone else can change everything except the internal identifier.)
My inclination is to remove these data from the UI altogether, and just leave a "click for entered and edited" option for "us."
I hope this isn't controversial and can be resolved quickly and easily, but adding to AWG agenda Just In Case.
Please review the Arctos Code of Conduct to ensure respectful communication, and see https://handbook.arctosdb.org/how_to/How-to-Use-Issues-in-Arctos.html for more information about submitting and managing Issues.