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
|
Since I got my problem with quoted identifiers solved, on to the next. :)
When populating the schema, actually have two issues:
First, it isn't pushing some properties, like ensuring columns are nullable and setting the Identity Column setting on the primary key (using auto-incremented keys).
Second, when creating the schema, I have to have it update twice. It won't created columns for relationships until the second time.
Another configuration setting? Right now, constantly changing my schema around so I'm regularly wiping it out and recreating it.
BTW, love LightSpeed so far.
Thanks,
Ken
|
|
|
|
|
Just noticed my line breaks are missing. Just getting a plain text editor in Safari, and wasn't putting in any HTML breaks.
|
|
|
|
|
I think nullability changes weren't implemented in 2.2 RTM, but they are in current nightly builds. Could you try installing the latest nightly build (Express edition from http://www.mindscape.co.nz/products/lightspeed/nightlybuilds.aspx, retail editions from the store) and see if that fixes that problem? IMPORTANT: If you are on LightSpeed 2.2 RTM, please UNINSTALL it before installing the nightly. If you do not do this, you will get HRESULT errors in the designer. (This should be a one-off thing: once you have installed a nightly, you should not need to uninstall it again if you upgrade to a subsequent nightly.) Identity/autoincrement is not currently automatically set. This is because we would normally expect the identity method to be set at the LightSpeedContext level rather than the per-table level, and the designer doesn't currently have any notion of context-level settings. We know this confuses and annoys people and we hope to improve this reasonably soon. Finally, unfortunately, yes, there is a limitation in the current version of the designer where it does not create foreign keys as part of table creation. This is because we do not currently order table operations, and if we tried to create Table A with a FK to Table B before we had created Table B, it would fail. We therefore for now duck the issue and just ask people to run the update twice. Again it is on the list of things to fix. |
|
|
|
