×
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.
But I'd like to discuss what is perceived as "significant operational
improvement".
Regarding DDL offering significant operational improvement...
I think the myth about DDL performance improvement has been exposed. Block
sizes are controlled by create and change commands - rather than the syntax
used to describe files, whether DDS or DDL.
In regards to errors, refer back to my gate analogy. Whether you open the
gate via push or pull, you have a roughly equal chance of getting an error.
In regards to code integrity, I much prefer coding constraints in DB event
handlers rather than defining field constraints in DDS or DDL. I prefer
having more control over error message content and error handling. I prefer
placing error information in export-import data structures rather than
looking for messages in call-stack message queues. DB defined check
constraints would be a step backwards, IMHO.
DDS vs. DDL? In regards to physical files and indexes, why push one or the
other? Does it really matter? Not to me. I should admit that the number of
SQL Views we deploy tends to be double the number of physical files.
midrange.com
