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
|
I recently upgraded from LightSpeed 3.1 to 5, and noticed a breaking change in one of my repository methods. I'm assuming this is a breaking change because the same code works in LS3.1. Here is a quick synopsis:
The Entity I'm querying for has no navigational properties, just regular CLR properties. However, there are about 1million records in the database. *I know its a good practice to filter on the server, rather than on the client side *. I would like to know what features have changed from the earlier versions of LS that would cause such a behavior. Thanks, M |
|
|
There is no functional difference in terms of whats going on to return the list of entities here, however I am guessing that there will be a slightly higher memory footprint for an entity due to the additional features added since LightSpeed 3.
|
|
|
Thanks for clearing that up! |
|