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. Otherwise - post away!
We can use ORM for:
1) Loading data from a database
2) Saving changed data to a database
I use LightSpeed for the 1-st purpose only. For saving changed data to a database i use stored procedures. Is it allowed use case? I suspect no. May be thereby i got following troubles:
If my use case is allowed, please provide sample.
related thread: Winforms Sample
It is of course possible to use LightSpeed only to load data and not to save it: just don't call SaveChanges() on the unit of work.
However, LightSpeed has no way of knowing whether you are going to call SaveChanges in future or not, so it always sticks to its normal "unit of work" (business transaction) rules. Specifically, if you want to reload entities, you must do so into a new unit of work, and if your sprocs require an ID, you must add new entities to a UOW in order to get IDs allocated for them.
There is no sample for this because read-only scenarios are accomplished by simply not calling SaveChanges() and so there's not really anything to show! However, JD is working on a Windows Forms sample which we hope to release in the next few days.