Yep, that integrity thing is important - one learns new error handling and ba-da-bing!

On 10/24/2014 2:01 PM, rob@xxxxxxxxx wrote:
There is the integrity of DDL on the validation on write though. With DDL
you just would absolutely not get that decimal data error.
Again, I'm all for the integrity of DDL over DDS. I'm skeptical on the
performance claims though.


Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Jon Paris <jon.paris@xxxxxxxxxxxxxx> To: Midrange-L Midrange-l <midrange-l@xxxxxxxxxxxx> Date: 10/24/2014 02:43 PM Subject: Re: Can I use DDS to create an SQL table name Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> I’ve never understood the “validation on read” claim. There is no validation - if there was you would never get a decimal data error on the field move that follows the basic read/chain. It would be stopped back at the DB level. The new query engine now works on just about all tables right? So there’s no specific advantage there. I’m with you Vern - there’s a lot of reason to use SQL. Far less to switch to DDL. Jon Paris
-snip-

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.