Pardon the long post everyone, but it seems from the other posts there
is a large misconception to address here and I will attempt to do so as
briefly as possible (Also, feel free to chime in where I am vague or wrong):
On 2015-03-18 11:24 PM, Jason Vas Dias wrote:
> OK, I discovered the OR clau
> On Mar 18, 2015, at 10:24 PM, Jason Vas Dias
> wrote:
>
> This seems very buggy to me.
Correct.
http://www.styleite.com/wp-content/uploads/2014/11/legallyblonde.gif
> On Mar 18, 2015, at 9:45 PM, Jason Vas Dias
> wrote:
>
> Would you care to expand on that ?
As it says on the tin [1]: you cannot start a transactions inside another
transaction (use savepoint if you want that), so?
create table foo( value text, constraint uk unique( value ) );
begin trans
On 18 Mar 2015, at 9:24pm, Jason Vas Dias wrote:
> But now I get another error after the constraint violation :
> 'Error: cannot commit - no transaction is active'
> which gets back to the original point of this post,
> which is that SQLite is evidently not considering
> all text within 'BEGIN
> On Mar 18, 2015, at 9:11 PM, Jason Vas Dias
> wrote:
>
> am I missing something?
rollback?
OK, I discovered the OR clause of the INSERT statement, so I'm trying:
BEGIN TRANSACTION;
INSERT OR ROLLBACK INTO db VALUES("This breaks a constraint");
COMMIT;
But now I get another error after the constraint violation :
'Error: cannot commit - no transaction is active'
which gets back to t
On 18 Mar 2015, at 8:11pm, Jason Vas Dias wrote:
> The problem is, if this transaction runs in a session, then
> NO transactions can ever run again in that session - eg.
> if I try to run the same transaction twice :
> On linux command line:
> $ echo '
> BEGIN TRANSACTION;
> INSERT INTO d
On 18/03/2015, Petite Abeille wrote:
>
>> On Mar 18, 2015, at 9:11 PM, Jason Vas Dias
>> wrote:
>>
>> am I missing something?
>
> rollback?
>
Would you care to expand on that ?
How is the script consisting of just the two insert statements shown
meant to determine if the first transaction has fa
Good day -
There appears to be a bug in the way SQLite implements transactions :
I have an insert transaction which breaks a uniqueness constraint on an index:
BEGIN TRANSACTION;
INSERT INTO db VALUES("This breaks a constraint");
COMMIT;
The problem is, if this transaction runs in a se
lists.sqlite.org [mailto:sqlite-users-
>bounces at mailinglists.sqlite.org] On Behalf Of Petite Abeille
>Sent: Wednesday, 18 March, 2015 15:02
>To: General Discussion of SQLite Database
>Subject: Re: [sqlite] bug in transactions implementation ?
>
>
>> On Mar 18, 2015, at 9:45
10 matches
Mail list logo
