SQL does not support date formats, the date is stored as integer value
(scaliger no) so the reported length is 4.
AFAIK there is no service or view that considers the "date format".
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 Jon
Paris
Sent: Montag, 25. November 2019 22:29
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: SYSCOLUMNS & SYSCOLUMN2
I'm playing around with these tables relating to some utility software.
I notice that if you have a date in a table that the reported length is 4 -
which while technically accurate is fundamentally useless as a program can
never see it as that length. The output from DSPFFD on the other hand shows
the length as 8 or 10 based on the date format.
Am I missing something? Is there another table or a column in either
SYSCOLUMNS or SYSCOLUMN2 that does accurately represent the size of the
column or do I have to calculate it?
Jon Paris
--
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
