on http://www.sqlite.org/src/wiki?name=Bug+Reports
I read
"The idea is that bug reports can be filtered on the mailing list and those
that are actual new bugs can be transferred into our bug tracking system by
registered developers.
* Anonymous users can continue to append comments to existing bugs, just
not create new bugs.* "
Am 12. April 2012 23:53 schrieb Joe Mistachkin <sql...@mistachkin.com>:
>
> Simon Hucksley wrote:
> >
> > since weeks I'm not able to edit the ticket as anonymous.
> > the edit button is missing on the menu.
> >
>
> Unfortunately, the ability to edit tickets anonymously had to be disabled.
>
> >
> > to ticket 4bbf851fa5
> >
> > It's the same old story:
> > after updating some hundred records
> > the DBConcurrencyException occurs.
> >
> > After updating the DateTime column
> > update t set dt = 2455926.6
> >
> > life goes on for some hundred updates.
> >
>
> As I said in the ticket, I've done quite a bit of careful analysis and
> troubleshooting on several issues that fall into this general area.
>
> The conclusion I came to was that the .NET Framework makes certain
> assumptions
> about ADO.NET providers (and their supported data types in particular)
> that
> do
> not always map correctly to how System.Data.SQLite handles its data types.
>
> Unfortunately, without breaking backward compatibility with previous
> versions,
> it is almost impossible to "fix" this issue from the System.Data.SQLite
> side.
>
> The best that can currently be done is to figure out exactly which of SQL
> queries generated by the .NET Framework are problematic and why (i.e. which
> use
> of the equality operator is causing the issue, given the parameter data
> types).
> As of release 1.0.80.0, This can be done by using the "Flags" connection
> string
> property, set to a value of "LogAll" (the important flags are "LogPrepare",
> "LogPreBind", and "LogBind"); however, "LogAll" is typically easier to
> specify.
> Here is an example:
>
> //
> // In order to actually see the output generated by these diagnostic
> flags,
> // you'll need to add a TraceListener of some kind to the TRACE listeners
> // collection (and the TRACE define constant must be present in your
> project
> // build configuration as well). For non-console applications, you'll
> want
> // to use the DefaultTraceListener instead (it will write output to the VS
> // output window when the application is running inside the debugger -OR-
> // you can use Sysinternals DebugView tool to see it when the application
> is
> // not running inside the debugger).
> //
> System.Diagnostics.Trace.Listeners.Add(new ConsoleTraceListener());
>
> using (SQLiteConnection connection = new SQLiteConnection(
> "Data Source=somefile.db;Flags=LogAll;"))
> {
> connection.Open();
>
> // code to execute query here...
> }
>
> --
> Joe Mistachkin
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
