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 finished the porting of my application from strongly typed datasets to LightSpeed. The porting was successful and I believe the code is much clearer now than before. I think that LS is very easy to use, but you must enhance the help system to avoid many of the questions in this forum. Many times I dont know what a method really does, I must prove and see the result. I found very useful the Help Topics / LightSpeed section, but the API reference is not very useful (for me). I like very much the log you create and I think it is invaluable to know where are the performance problems. Improve it! There are some things that sounds strange at first time: when querying the database if you use the Query class you must use the name of the fields (that are private), but if you use LINQ you must use the name of the properties. About LINQ, depending what you do sometimes you use LINQ to LightSpeed, and other times LINQ to Objects (when the sentence is over a entity collection). For a novice to LINQ (as me) this is complicated at first time.
I am now fixing all the bugs I introduced in the porting, many of then are the result of the different data binding I must use now. This is hard work. Some time ago I reported several problems, one related to CancelEdit assigning null to entity holders. You suggested to change the relation to eager load and this fixed the problem, but now I am suffering the same problem in different parts of the application. I can reproduce it always, but creating a sample is difficult, but if it is neccesary I will do it. You must review the code of CancelEdit(), some part must be wrong. Actually I am considering implementing my own (simplified) version of BeginEdit()/CancelEdit()/EndEdit(). These methods are very important in windows forms applications where the user sometimes cancel the editions before saving.
Thank you. |
|
|
Some news about the CancelEdit() problem? |
|
|
Hello Enrique, I'm afraid we've not had the chance to look at the CancelEdit problem yet. If you are able to create a simple repro case then that will certainly help us to address it quickly. |
|
|
Hello Enrique, I'm investigating the problem you reported with CancelEdit and I've reproduced a problem but want to check that it's the same one that you're seeing. Here's my test (where the Comment.Member association is lazy loaded): Comment c = _unitOfWork.FindById<Comment>(81); Whereas if the first Assert is placed before the BeginEdit, it works okay. Does this look like it's your scenario? Thanks! |
|
|
I've committed a fix for the scenario described above and it will be included in nightly builds dated 2 Mar 2010 and above, available from about 1500 GMT. If this isn't your scenario, or if you've found other issues with CancelEdit, then please let us know the details and we'll get it sorted for you. |
|
|
Hello Ivan, it seems the same scenario. I'll try the fix. Thank you. |
|
|
Hello Ivan, with the new version cant reproduce my previous problem with CancelEdit(), it seems that you fixed it. Great. Thank you.
|
|