× 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: Date performance
  • From: "Brigitte Caura" <Caura@xxxxxxxxxxxxx>
  • Date: Mon, 26 Oct 1998 20:59:06 +0100

Thanks a lot , Simon

A nice clear explanation.

2 small remarks:
. V3R7 manual does mention storage of 10 chars, just as V4R2.
. It would have been nice if this difference of 'program storage (what s in
a name)' and 'storage storage' was explained explicitly.

 Regards
Luc
-----Oorspronkelijk bericht-----
Van: Simon Coulter <shc@flybynight.com.au>
Aan: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Datum: maandag 26 oktober 1998 14:32
Onderwerp: Re: Date performance


>Hello Luc (or Brigitte ??) and others,
>
>You are seeing the difference between the number of bytes used internally
to store the field versus the
>number of character positions required in a buffer to present the field.
>
>The V3 DDS Reference showed the internal sizes of Date, Time, and Timestamp
fields.  The V4 manuals show the
>buffer sizes of these fields.
>
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.