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`ve got a simple model consists of a few entities. I`m trying to increase performance of my application. I noticed, when I updated only one property of come entity, LightSpeed updated all columns of the entity`s table in the database. Then I set Optimistic Concurrency Checking of the entity to True and ran the test again. LightSpeed updated changed property and.. all foregin keys of the entity! But I updated a simple property, not foregin key! If we have a big tables (that contains hundreds of thousands of rows), updating of foregin key will be a heavy operation - updating foregin key index, checking referential integrity - it is superfluous operations. Is it a bug? Is there any way to update ONLY changed property of an entity? Thanks. |
|
|
This is actually by design due to the way in which we handle managing the associations and associated FK fields. That said this behavior stems all the way back to version 1 of LightSpeed, so looking at things now we can certainly make a change to this. I have made the updates to remove the need to send down all FK's during partial updates and this will be available with the next nightly build.
Thanks for raising this! Jeremy |
|
|
>> this will be available with the next nightly build It would be great! Thanks! |
|