This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
A couple of issues I've seen working with a DB2 database:
I tried to work around 2 by creating a "Keytable" table in the designer but I guess your check for the table did not recognize the table as it did not work. Any workarounds? |
|
|
re 1: This can happen if we cannot correctly infer the property names but Im not sure why that would happen. Are the tables using a different schema from the connection default perhaps? re: 2: This sounds like a bug, so Ill have a look into getting this fixed and update you again once this is in the nightlies. re: 3: Yes, KeyTable will be generated with the default schema as per the connection. It will also be accessed as such later on so you will either need to change the connection string to cater for this, or if this is not possible you will need to create the KeyTable manually and then make sure you set the LightSpeedContext.Schema property on your context instance to change this to the schema being used for the KeyTable. re: 4: This looks like a bug in the update provider for the designer, Ill look at getting this fixed and update you again once this is in the nightlies.
|
|
|
re: 4 - Ive added an update which will be available in the next nightly build to address this. You should now see these being generated as TIMESTAMP's.
|
|
|
Thanks Jeremy, that worked. The CreatedOn and UpdatedOn are being created but with quotes. From the SQL script: WaveStatusUpdateDateTime TIMESTAMP WITH DEFAULT NULL, WCSDnldCount INTEGER WITH DEFAULT NULL, "CreatedOn" TIMESTAMP NOT NULL, "UpdatedOn" TIMESTAMP NOT NULL); This results in non-quoted fields being upper cased by DB2 and the quoted fields being mixed case. In another post I had asked about this. It would be great if there was a setting somewhere that would allow all fields to always be quoted or un-quoted. |
|
|
Hi John, Yes Ive added an item to our backlog to look at adding in an option to the designer to support identifier quoting across all entities where desired which will be whats needed to cover this.
|
|