Re: Finding invalid data in zoned numeric fields with SQL -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: Re: Finding invalid data in zoned numeric fields with SQL
From: Charles Wilt <charles.wilt@xxxxxxxxx>
Date: Mon, 13 Jul 2009 13:29:25 -0400
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>

On Mon, Jul 13, 2009 at 1:21 PM, Jim Essinger<dilbernator@xxxxxxxxx> wrote:

Yes - I believe the software vendor did create this with DDS, and even
thought it is defined as Zoned, it somehow allows invalid data to be added
to the file in 4 fields.

That's working as designed.

With a DDS defined file, the data is not validated when written but
instead whenever it is read.

On the other hand, a data written into an file defined with SQL DDL is
validated when written.

Note this means if you have a file that is read more than written, you
can save soem CPU cycles by defining the file with DDL.

Charles

Follow-Ups:

Re: Finding invalid data in zoned numeric fields with SQL , rob

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.