$createnames strange DAM bug

[Vik Shah]

Hi Mark,

Thanks for the reply. 

The columns are defined no differently then the rest of the other tables and surprisingly it works when I take a copy of the library that is a few releases back.

From the Omnis Studio point of view the schema class looks normal but there is something going wrong here. I’ve so far replaced the table class and still its doing the same. Even if I create a new schema+table class it also fails in the same way.

I will be running more tests today, but I’d still like to see what others have to say on this topic.

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

I’ve been leaning towards this very conclusion too, its something todo with the library as the container and/or the schema class. There may be some internal corruption going on here, if so then we are in for a whole lot of pain. I’ll run some tests and if possible see if I can reconstruct the library from scratch and then check it into the VCS.

PS: I have been having issues checking things to/from the VCS, I get errors to the effect that the checksums don’t match and some classes fails to checkout, if forced to checkout then the classdata seems to be corrupted.

could it be...

Thanks for any thoughts or assistance in advance.

Regards,

Vik Shah
Director
Keys2Solutions
AU: +61 411 493 495
SE: +46 21-495 01 05
US: +1 (415) 413 4172

> On 21 Dec 2016, at 2:32 AM, Mark Phillips <mark.phillips at mophilly.com> wrote:
> 
> 
>> 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."
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com