Re: [sqlite] TransactionScope ON CONFLICT

Last error i would see is i have made an error with the assembly creation. Is it possible for you joe, to send me your assemblies direct per email? So I can exclude this error. ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > > The important thing is that there is only one SaveChanges call (which > attempts to commit pending changes to the underlying database). > Yes, i do so. > > My test case does attempt to add rows that conflict with data already present > in the sample database. > Ok,

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > > So you add all the 15 rows inside one transactionscope and with one > context.SaveChanges() call? > Yes. > > Perhaps it makes a difference if the contains violation is inside the > 15 rows you try to add (row 10 is incompatible with row 2 for example) > The important

Re: [sqlite] TransactionScope ON CONFLICT

Joe Mistachkin wrote: > > Are you sure the application is loading the new DLLs and not some stale DLLs > leftover from before? > Yes, i look with Visual Studio in the "Loading Modules" window. Path and version are correct (1.7.5) before I had installed only some 1.6 runtimes. Hopes I do all

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > > I try this now but with no success. > Are you sure the application is loading the new DLLs and not some stale DLLs leftover from before? > > Did it work at your test case? > Yes, my test case works properly (the first time). The second time, all the rows have

Re: [sqlite] TransactionScope ON CONFLICT

Igor Tandetnik wrotes: >I'm not sure I understand this statement. What kind of "influence" do you want >to exert? To work like expected. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] TransactionScope ON CONFLICT

Joe Mistachkin wrote: >The test case I added for this issue is remarkably similar to your code, >except it uses a different schema (the Northwind sample database) and does not >re-throw the exception in the catch block (it simply writes it to the console >instead). >The one >modification I

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > Hm... but the exception i get is an SQLite constraint exception. This means > that > The error occurs at the moment where SQLite provider try to write data to the > DB. Which is inside SaveChanges call. > So I cannot have influence to this

Re: [sqlite] TransactionScope ON CONFLICT

Hm... but the exception i get is an SQLite constraint exception. This means that The error occurs at the moment where SQLite provider try to write data to the DB. So I cannot have influence to this loop that you mean. Igor Tandetnik wrote: >Inside this call, a loop runs, with one INSERT

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > > No i think i can exclude this as the problem. > Because my code goes like this: > The test case I added for this issue is remarkably similar to your code, except it uses a different schema (the Northwind sample database) and does not re-throw the exception in the catch

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > No i think i can exclude this as the problem. > Because my code goes like this: > > try >{ > context.SaveChanges(); // save changes with transaction !exception raised here Inside this call, a loop runs, with one INSERT

Re: [sqlite] TransactionScope ON CONFLICT

No i think i can exclude this as the problem. Because my code goes like this: using (dataDBEntities context = new dataDBEntities()) //create context { using (TransactionScope transaction = new TransactionScope()) //begin transaction {

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > Ok I'm tested it now in a simple test environment. > > Conditions: > 1 table with two columns "TimeStamp" (PK) and "SensorID" (simple value). > > First I add a row with "TimeStamp" "2011-01-01 01:05:00" (Success) > Then I doing a Transaction

Re: [sqlite] TransactionScope ON CONFLICT

Ok I'm tested it now in a simple test environment. Conditions: 1 table with two columns "TimeStamp" (PK) and "SensorID" (simple value). First I add a row with "TimeStamp" "2011-01-01 01:05:00" (Success) Then I doing a Transaction with 10 "TimeStamps" from "2011-01-01 01:00:00" to "2011-01-01

Re: [sqlite] TransactionScope ON CONFLICT

Ok im not clear if im doning it right. I follow your instructions and get a compliable version. But how to get your branch? What I'm doing now is to download the zip under "Other links: Zip archive" under http://system.data.sqlite.org/index.html/info/42af4d17a5 and copy it over the version from

Re: [sqlite] TransactionScope ON CONFLICT

Sorry, I make my test with wrong conditions it looks like It not works correct at all. Please give me a sec to do some more tests and ignore my last message *shame*. I come back here after testing. Steffen Mangold wrote: >Nice job! :) It works now like expected. I have tested it with use of

Re: [sqlite] TransactionScope ON CONFLICT

Nice job! :) It works now like expected. I have tested it with use of this patch http://system.data.sqlite.org/index.html/info/42af4d17a5 . I also wrote a comment to the ticket [ccfa69fc32]. Thank you, great job. Steffen Joe Mistachkin wrote: >I believe that I've found and fixed an issue in the

Re: [sqlite] TransactionScope ON CONFLICT (oops, missed a step)...

Oops, forgot to update to the bug-ccfa69fc32 branch, inserted new step #8 below to correct this. Steffen Mangold wrote: > > It would really help me if you send me your step by step instructions. > I had some experience with SVN, but it will help for building. > 1. Download the Fossil binary

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > > It would really help me if you send me your step by step instructions. > I had some experience with SVN, but it will help for building. > 1. Download the Fossil binary for your platform (e.g. Windows):

Re: [sqlite] TransactionScope ON CONFLICT

hi joe, wow thanks for your fast help. Tomorrow I will try your patch. It would really help me if you send me your step by step instructions. I had some experience with SVN, but it will help for building. Thank you!! Steffen Mangold Joe Mistachkin wrote: >I believe that I've found and fixed

Re: [sqlite] TransactionScope ON CONFLICT

Steffen Mangold wrote: > > I have a question to the System.Data.SQLite in action with the .Net > TransactionScope. In the SQLite documentation is written that the > default behavior of a transaction in case of an error is "ABORT". > In documentation is also writen that "prior SQL statements

Re: [sqlite] TransactionScope ON CONFLICT

>> In this example I added 10 objects to the context and I know that object #5 >> raises a PrimaryKey (or unique) Exception.>> What I read from the SQLite >> documentation I understand that object #6 till object #10 will be also add >> to the database.>> But this never happens.>> I assume you

Re: [sqlite] TransactionScope ON CONFLICT

On 10 Sep 2011, at 4:22pm, Steffen Mangold wrote: > http://www.sqlite.org/lang_transaction.html > " Such transactions usually persist until the next COMMIT or ROLLBACK > command. > But a transaction will also ROLLBACK if the database is closed or if an error > occurs and the ROLLBACK conflict

Re: [sqlite] TransactionScope ON CONFLICT

Hi Simon, first nice to hear from you. :) > Fred helps solve Helen's problem one day, Helen may solve Fred's the > following week. Oh I'm not mean pro support. What you descript is what I'm searching for. Like a forum. > Can you show us a pointer to this information ? Sure,

Re: [sqlite] TransactionScope ON CONFLICT

On 10 Sep 2011, at 3:58pm, Steffen Mangold wrote: > I'm hoping doing all right to get technical support. :) Perhaps not. If you want technical support you have to pay for it. This mailing list is mostly a bunch of users who have run into their own problems over the years. Fred helps solve

[sqlite] TransactionScope ON CONFLICT

Hi, I'm hoping doing all right to get technical support. :) I have a question to the System.Data.SQLite in action with the .Net TransactionScope. In the SQLite documentation is written that the default behavior of a transaction in case of an error is "ABORT". In documentation is also writen