×
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.
On 2012-06-27, at 10:53 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
I confess to my ignorance. The problem was not with my dates or logic. It
was my assumption that interactive SQL would show the date values in the
file in format defined in the DDS. Nope. It shows them in the format set
in the Current SQL Session attributes.
I must admit I was a bit surprised that it was SQL giving you the wrong impression about the dates.
The big thing to remember about dates is that they are actually stored as a Lilian* date as a binary integer. The format information associated with the field is only use when surfacing the field as part of a record. In other words we can't really ever see it in the binary version. I can only guess that because SQL does not surface the row as a record in the conventional sense it doesn't go through that process and just uses a single format when handling date fields generically.
*Lilian - I recall someone in Rochester once telling me that it was a "flavor" of Lilian date - not a "real" one. But since I can't ever manipulate the date at that level I don't really care.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
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.
midrange.com
