Not sure how to respond here. Pretty sure I have a handle on the information provided and that is not meant as criticism of your explanation in any way. After all, you can't know what I know and so can only document what is and you have done that with your usual accuracy and thoroughness. My question is more abstract?
Given that, to a computer, all constructs concerning a whole host of things what we humans recognize as either dates or times, regardless of format, are just different expressions of milliseconds, that, in my mind, coming from a software user perspective as opposed to the perspective of a software designer, is almost immaterial. Now as also stipulated, all such representations of milliseconds which are designed to be for "the convenience of humans" being mere abstractions of the true nature of the computer's understanding of time and date, being not quite "real" from that perspective, I ask again, why can't there also be a "fake" date and a "fake" time much like there is a "fake" day of week or a "fake" month of year construct or abstraction?
Given our foregoing stipulations, all of the SQL functions listed in the manual are just "fake" or "abstract" translations of a "real" time for the convenience of humans. I am human (depending on who you ask) and I want convenience. In fact, I have grown quite accustomed to it using Manifold. For instance, let's take my address for comparison. The computer knows it for mapping purposes as a series of coordinates which it abstracts to a point on a map that I can recognize given that the map contains enough context. I do not recognize the storage structure of that information in its native form and I will argue that I do not need to unless, for some odd reason, I take up a career in GIS. An important parallel here is the fact that my address could also be stored as a string which the computer does not understand at all, but which is done solely for my edification as a human since it has more meaning to me than say a tuple of coordinates in Euclidean space.
So when I make a request of sales that a SQL function to create a "fake" date, or time be added, how is that any different to asking say for a function to return a day of week that already exists? If someone can come up with a difference, then yes, I do not "get it" and will likely need some serious explanation.
I am pulling data from a database that has a datetime in it but without looking at it, as this is an automation routine and hence negates the formatting option proffered, I need to transform it into a "fake" date which is doubly fake in this case as it will be exported as text in a .csv (like the address) to be displayed in an Excel spreadsheet.
Manifold constantly performs miracles of abstraction well beyond my understanding. That makes me no less aware or appreciative of them. And my request is not in that category as it is rather simple math to convert milliseconds. I say simple not to slight anyone else, but just because I know that in the present company and context, if I can understand it, it is simple indeed.
Finally, if no one wants to make such a SQL function, fine. I will cobble up the make date function along with the other requisite functions to make my own I guess. But again, human -> convenience -> lazy . . .