|
One of our clients had a program crash while the programm was inserting a bunch of data. Although the programm hadn't run to the point where the commit would have been executed, the data is still there [SA 12.0.1]. So I wonder if there is a connection option triggering a commit it the connection is closed, similar to that option setting in ISQL. I searched the help and checked sa_conn_options, but to no avail. Did I overlook something, or is there another explanation? |
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 31 Jul '12, 09:57
question was seen: 2,037 times
last updated: 07 Aug '12, 09:29
SQL Anywhere shouldn't commit a transaction unless the application tells it to. Have you looked at the transaction log to try and figure out what may have happened?
If it's a PowerBuilder application the default for CommitOnDisconnect is 'Yes'.
The application has been build with Power++, not PowerBuilder. But the Power++ IDE uses a subset of PowerBuilder 6.5 to create DataWindows and Reports. So there might be a similar property behind the scenes (undocumented).
I don't have access to the log file. But I don't think I could learn much from that: surely there will be a commit, but it's hard to tell where it comes from.
I'm sure you're running in ODBC's manual-commit mode (and not the default auto-commit mode), right?