Re: Dates and Timestamps. -- 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: Dates and Timestamps.
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Mon, 28 Oct 2019 14:05:15 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
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>

On Mon, Oct 28, 2019 at 2:01 PM Alan Campin <alan0307d@xxxxxxxxx> wrote:

My boss is telling me that he thought that date data type in the database
was somehow deprecated and that you should just use Timestamp. I have never
heard of such a thing. Ring any bells with anyone? He is from the SQL
Server world so maybe that is where he is picking it up.

I've never heard of that either.

I can't imagine date & time being deprecated ... sometimes you need
date, sometimes you need time, sometimes you need a timestamp.

david

As an Amazon Associate we earn from qualifying purchases.

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.