time/date as key fields -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: time/date as key fields
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Fri, 19 Nov 2010 10:21:28 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Is there anything wrong in using date and time of creation fields already existing in a transaction table to keep track of transaction history or would it be advisable to add a separate field transaction_number? The latter means a lot more program changes.

Thanks

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: time/date as key fields , dieter.bender
Re: time/date as key fields , Tommy . Holden

This mailing list archive is Copyright 1997-2026 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.