Re: SQL insert using "current timestamp" across machines

Hello,

Am 22.07.2023 um 03:06 schrieb smith5646midrange@xxxxxxxxx:

I don't mean to sound snarky but when I specifically state

if anyone has a better solution (other than keep your system's times in sync)

why is it that all of the responses are to keep the system's times in sync?

Because everything else just is a botchy work around your observed symptoms, making no sense in the end. Personally, trying to compensate for a deficiency on the system level by applying a crude programming workaround as described makes me wince. Especially given the technical solution is much easier to implement.

I am a consultant. I don't have any say in what my clients do with their systems.

Correct. But you can consult them to use their system properly. If many people agree on the same solution, I'd call this "best practice". If the client is not aware of such best practices, I'd make them aware.

So, since there was not a better code solution, I will be modifying my code to use the variable solution.

Yes. And with time, the time gap between systems will change.

:wq! PoC