RE: SQL insert using "current timestamp" across machines -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: SQL insert using "current timestamp" across machines
From: smith5646midrange@xxxxxxxxx
Date: Fri, 21 Jul 2023 21:06:32 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

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?

I am a consultant. I don't have any say in what my clients do with their systems. So, since there was not a better code solution, I will be modifying my code to use the variable solution.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: SQL insert using "current timestamp" across machines , Patrik Schindler

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.