× 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.



From: Jeff Crosby

In any case, I related to them that in trying to modernize into SQL DML
from
DDS, this would definitely slow me down, as well as anyone else using date
data types, due to massive numbers of recompiles. It wouldn't surprise me
if time and timestamp fields turned out that way too.

Jeff, I seem to remember this exact symptom (mismatched format IDs) coming
up a while back, although I can't recall if it was triggered by date fields.
I remember thinking at the time that while it didn't affect me personally,
it would certainly be a huge issue for people trying to move from DDS to
DDL, and then subsequently wondering why there wasn't more clamor.

I would like to know who is telling you that this is designed behavior,
because we'll need to explain to them very carefully that the designed
behavior is incorrect: there must be transparency at the format level
between DDL and DDS generated files.

Joe



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.