$createnames strange DAM bug

Mark Phillips mark.phillips at mophilly.com
Tue Dec 20 11:32:52 EST 2016

> On Dec 19, 2016, at 10:11 PM, Vik Shah <Vik at keys2solutions.com.au> wrote:
> Fingers are pointing towards some sort of class corruption, unless someone here can think of something else.

If it is indeed corruption, then that is easily determined. However, with the data type of NULL returned, there may be a problem with the built in data type mapping between Omnis and the DBMS, or possibly a rare problem with ODBC connection. 

IMO, not that anyone asked, this problem stems from using Omnis Schema classes to automate DDL generation. It works provided the data type mapping is correct for the target DBMS revision, but therein lies the risk. Automated DDL generation can be fussy and MS SQL Server is rife with interesting sniglets. For this reason, I prefer to build DDL text files for the database updates, test and package, and the deploy them through an update processor.

Warm wishes on winter day,

 - Mark

"Wait. You're making a mistake. My mistake is better."

More information about the omnisdev-en mailing list