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
|
Hi, I downloaded your LightSpeedExpress-20081006.msi and found a model designer issue: Steps to re-produce it: 1) create a new model 2) set the connection type to SQL server 2005 and set proper connection string 3) add a new entity 4) add a new property to the entity 5) Amend entity properies: Track Create Time to True, Track Update Time to True 6) Update Database 7) the table created, but no CreatedOn or UpdatedOn field 8) Update Database again, designer show CreatedOn and UpdatedOn fields will be created, click OK 9) Error message box shown: The following updates could not be carried out: Entity1: Add column CreatedOn of type DateTime - SQL Server cannot add column CreatedOn unless it is made nullable Regards |
|
|
Thank you for reporting this issue -- and for the very clear and precise repro steps! I have committed a fix that will create the "special columns" for Track Create Time, Track Update Time, Optimistic Concurrency Checking and Soft Delete during table creation. This will be in nightly builds numbered 20081007 and above, available from http://www.mindscape.co.nz/products/lightspeed/nightlybuilds.aspx. Please note that due to our recent server move, there may be a few days delay before the nightly is available at the URL above. Please let us know if you would like it urgently; otherwise, in the meantime, you can of course add the CreatedOn column manually via Server Explorer or SQL Server Management Studio. Note also that the fix applies only to table creation. You will still not be able to add the CreatedOn column via the LightSpeed designer after the table has been created. This is because we do not yet detect empty tables (where SQL Server does allow the adding of non-nullable columns), and therefore always fail to add non-nullable columns to existing tables (and CreatedOn is always non-nullable). Let us know if this is an issue for you. Thanks again for letting us know about this. |
|
|
Hi, The limitation "In model designer, CreatedOn field cannot be added to table after the table has been created" is ok for me. But for long term, I think it's still need to be handled for a good product. Thanks and Regards, |
|
|
Thanks for the feedback. I've logged it as an issue to improve the handling of adding non-nullable columns (such as CreatedOn) to already-existing tables. |
|