Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In the latest version V.4.42.14, user can directly edit data in the grids mode, which is awesome. Every time I edit one row data and move my cursor to next, the edited data automatic commit to database. The automatic commit is very dangerous without I click a save button. Sometimes I edit a data just for demonstration purpose, actually I don’t want it commit when I move my cursor to next line. Does anybody can help how to avoid edited data automatic commit in LinqPad Edit Mode?
LINQPad behaves this way to be consistent with SSMS, and to avoid the possiblity of losing large number of edits should you close the query or hit F5 (or close LINQPad) without saving.
It wouldn’t be hard to offer the option of table-level buffering if there’s enough demand. It would require, though, an enhancement to the extensibility model to allow queries to signal to the host that they have unsaved data, so that LINQPad can offer “Abandon Changes” prompt to avoid the scenario described above.