On Thu, 4 Oct 2007, Brady Eidson wrote:
From the definition of the Database object -
void closeTransaction(); // only needed as part of error recovery
Then later described -
The closeTransaction() method may be called while in a callback called by the
executeSql() method. When the method
On Fri, 5 Oct 2007, Scott Hess wrote:
Reviewing SQLite's error list, the things that MAY have utility to
report more finely might be:
* LOCKED, where you failed because someone else has things locked.
Presumably if a single thread of control tries to open the same database
via two
On 10/15/07, Ian Hickson [EMAIL PROTECTED] wrote:
On Fri, 5 Oct 2007, Scott Hess wrote:
Reviewing SQLite's error list, the things that MAY have utility to
report more finely might be:
* LOCKED, where you failed because someone else has things locked.
Presumably if a single thread of
On Oct 15, 2007, at 2:07 PM, Ian Hickson wrote:
On Fri, 5 Oct 2007, Scott Hess wrote:
Reviewing SQLite's error list, the things that MAY have utility to
report more finely might be:
* LOCKED, where you failed because someone else has things locked.
Presumably if a single thread of control
At 7:38 + 13/10/07, Ian Hickson wrote:
When the first element of a value is 'avc1', indicating H.264 (AVC) video
[29], the second element is the hexadecimal representation of the following
three bytes in the sequence parameter set NAL unit specified in [29]: 1)
profile_idc, 2) a byte
On Mon, 15 Oct 2007, Scott Hess wrote:
Under SQLite, there are cases where retrying might work, in which case
you can retry. There are other cases where retry will never work, you
need to rollback your transaction and start over. If you don't do so,
you can cause a deadlock. Much of
On Oct 15, 2007, at 8:37 PM, Ian Hickson wrote:
* CORRUPT, insofar as the Database API lets you delete databases
(it
doesn't currently, but we've thought of adding that to Gears).
You may be correct that authors shouldn't be dealing with this.
Guaranteeing the integrity of the database at
