Author Topic: Commit vs Abort  (Read 9156 times)

0 Members and 1 Guest are viewing this topic.

Glenn R

  • Guest
Re: Commit vs Abort
« Reply #15 on: September 21, 2006, 01:07:23 AM »
I agree...I rarely if ever used transactions in ARX.

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: Commit vs Abort
« Reply #16 on: September 21, 2006, 04:18:55 AM »
.....  I've had problems using transactions for read-only object access, regardless of whether they are committed or aborted (the manifestation is that it disables REDOing of the operation(s) after the transaction is ended, if they are undone).

Thanks Tony .. time for me to have a rethink ..
kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

Alexander Rivilis

  • Bull Frog
  • Posts: 214
  • Programmer from Kyiv (Ukraine)
Re: Commit vs Abort
« Reply #17 on: September 21, 2006, 07:35:41 AM »
Tony! VS2002 C# (not VB.NET) has using statement in context:
Code: [Select]
using (...) {
}
For example this code is working under AutoCAD 2006 / VS 2002:
http://discussion.autodesk.com/servlet/JiveServlet/download/152-500641-5307312-121115/Zoom.txt

TonyT

  • Guest
Re: Commit vs Abort
« Reply #18 on: September 21, 2006, 11:07:56 AM »
Tony! VS2002 C# (not VB.NET) has using statement in context:
Code: [Select]
using (...) {
}
For example this code is working under AutoCAD 2006 / VS 2002:
http://discussion.autodesk.com/servlet/JiveServlet/download/152-500641-5307312-121115/Zoom.txt

Hi Alex.  I believe it was VB.NET that was missing it in VS2002.