[TIMOB-364] Enable Transactions for Titanium.Database (Mobile)
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:52:49.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.6.0 M10 |
| Components | iOS |
| Labels | database, defect, ios, release-1.6.0, transactions |
| Reporter | Johann Richard |
| Assignee | Reggie Seagraves |
| Created | 2011-04-15T02:27:57.000+0000 |
| Updated | 2011-04-17T01:52:49.000+0000 |
Description
It would be very helpful if Transactions were enabled in Titanium.Database (Mobile) -- be it by exposing/wrapping the PLSQLite Transaction methods in Titanium.Database or by allowing the corresponding SQLite SQL Statements (BEGIN; ROLLBACK; COMMIT)
I second this, it's breaking some functionality/tests in JazzRecord ORM at the moment.
When I checked on 1.2.x, db.execute("begin") /rollback/commit was working fine...
My bad; the drillbit test I wrote was pulling SELECT operations in the middle of the transaction. Bad mojo.
Further testing reveals that this is an Android issue, still. Assigning to Don for triage; going to commit a Drillbit test.
(from [90e349c4c2a6438fbb68a59a5f2b83379dce68f3]) [#364] Drillbit test for begin/rollback/commit and savepoints in database. https://github.com/appcelerator/titanium_mobile/commit/90e349c4c2a6438fbb68a59a5f2b83379dce68f3"> https://github.com/appcelerator/titanium_mobile/commit/90e349c4c2a6...
Created #3151 to track the android side