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
|
We're investigating Light Speed, and it's against policy to update the database from an ORM - The ORM we choose should instead take the changes from the database into the models. Is there a bug with the designer? Whenever I say 'Update from Source', it assumes that all the fields are to be deleted. This leaves me with a blank entity, which can't be re-updated from the source. |
|
|
|
|
Did you create the entity from the database (e.g. drag on a table from the server explorer) or by manually adding the entity properties? Assuming that is how the entity was originally created as a workaround you can delete the entity and re-drag the table on to the design surface to fetch any updates.
|
|
|
|
|
I have a similar problem. I have several views that I dragged onto the designer. Each view has a "ViewId" property, which is a string property that is a concatenation of various other columns to insure a unique ID so that LightSpeed can be happy. I am using the "IdentityColumn" identity method, and the ViewId column name and type are properly set. This works fine since we're not doing any joins or updates -- just purely reading data. However, I have noticed that on several of these views, when I say "Update from Source," the only thing it does is threaten to delete my entity from the model, but doesn't give me any useful update options (see attached screenshot). Usually, after the view is first created, the Update from Source option works one or two times, but eventually it stops working and just wants to delete the entity. This is annoying because I have several views with over a hundred fields, and it is a pain to try to manually keep them in sync. I'm not sure why the sync function breaks, but maybe because I have manually added a few properties, or made manual changes? Any clues would be helpful. Thanks, Ken |
|
|
|
|
You wont be able to sync this entity as it was created to support the view but does not exist in the database. You will need to ignore this entity on database updates as we are expecting a table to be present to derive the information from for the two way sync.
|
|
|
|
