Just compare the Hex Value of a Date with the Hex value of a timestamp.
You'll find the first 7 character or the timestamp matches exactly the Hex
Value for the date!
Values(hex(Current_Date), Hex(Current_Timestamp));
Result: 002584A2 002584A2053307042819
Inn either way you should need a timestamp (if you need one) instead of
concatenating a Date and a Time.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Alan
Campin
Sent: Montag, 28. Oktober 2019 20:01
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Dates and Timestamps.
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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
