Just one thing to make it clear - maybe i shouldn't write mails so fast :) In the ideal word when you start designin your application from scratch - drow all thge diagrams or do it in any other way, traditional or agile - it doesn't matter - but when you start from scratch you can do everything you want. In this case I full agree with everything that has been said already -- keeping multiple-requests db transactions is bad practice. Period. I think everybody agrees here :)
The real word for me however is different: I have to work for different systems working side by side. Sometimes for example I have to write stupid application that is not really more complicated that the famous facebook clone. The only difficulty is that it MUST work on existing data, use (partially) existing tables, stored procedures etc etc. In such cases if I would say to my boss or client : drop this billion dollar 20 years old system and buy new one with different data structure - it could be last of of this job :) I must find a solution that: a) works b) there is someone that is willing to pay for it. I believe thats the real reason why I am so liberal for this kind of approach like killing user db session just because its to long... but in one project it was the only solution that someone wanted to pay for. So - to summarize: I agree if talking about theory, I disagree if talking about real life - but it's not a general chat so I suggest to close this issue. If I will encounter it in real project I will raise it back, for now - it's not worth it. Thanks for all the answers, even if I disagree less or more ;) Regards Adam
