On 13/06/2014 4:38 PM, RSmith wrote:
If none of these finds you a culprit, it means your program is the only
thing left to blame. Here we need to start with logging every time you
create a connection and start a query or creating a prepared statement.
Log the handles or object IDs you get back fr
On Fri, Jun 13, 2014 at 6:08 PM, Maxim Khitrov wrote:
> Hi all,
>
> I don't think this is a problem with sqlite, but I'm also not sure
> what external behavior could trigger this, so I'm looking for help
> from someone more familiar with the sqlite internals.
>
> One of the users of my SQLite bin
Hi all,
I don't think this is a problem with sqlite, but I'm also not sure
what external behavior could trigger this, so I'm looking for help
from someone more familiar with the sqlite internals.
One of the users of my SQLite binding for Go is reporting a
non-deterministic segfault in the 3.8.5 a
Joe, thanks for the idea. I did contact them about the version being old
but no response yet.
Cheers
Jim
-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Joe Mistachkin
Sent: June 13, 2014 4:07 PM
To: 'General Discussion of SQL
On 2014/06/13 17:38, Sohail Somani wrote:
Thanks for your response. I had been trying to avoid the "writing little bits" over time to avoid an inconsistent state in the
case of a crash or user exit, but the inconsistency is not that big of a deal as the data integrity is still there and eventu
That error likely implies that your .NET assembly is corrupted.
After you observe the error, can you attempt loading your version of
System.Data.SQLite.dll in ildasm.exe ? If you are not certain of the file on
disk from which Assembly is being loaded, run Fuslogvw.exe to generate the
binding l
Calvert, Jim wrote:
>
> Is there anybody from the developers of SQLite who can comment on this
issue
> for me.
>
I did reply to your original post. Here is a link to the thread:
http://www.mail-archive.com/sqlite-users%40sqlite.org/msg84247.html
--
Joe Mistachkin
__
> On 13 Jun 2014, at 7:22pm, Calvert, Jim wrote:
>
> Is there anybody from the developers of SQLite who can comment on this issue
> for me.
We saw your post. No need to repeat it. Your problem is not with SQLite and
that's why we didn't answer.
Consult whoever wrote your MS Outlook synchron
Everyone,
Is there anybody from the developers of SQLite who can comment on this issue
for me.
Thanks
-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Calvert, Jim
Sent: June 12, 2014 11:46 PM
To: sqlite-users@sqlite.org
Subje
On 6/13/2014 1:27 PM, Richard Hipp wrote:
On Fri, Jun 13, 2014 at 1:20 PM, Eric Rubin-Smith wrote:
If I say sqlite_bind_text(...SQLITE_STATIC), I am promising that the buffer
is going to stick around for a while. How long am I promising that it will
stick around? Til the next statement reset
On Fri, Jun 13, 2014 at 1:20 PM, Eric Rubin-Smith wrote:
> If I say sqlite_bind_text(...SQLITE_STATIC), I am promising that the buffer
> is going to stick around for a while. How long am I promising that it will
> stick around? Til the next statement reset()? Til the statement
> finalize()? T
On Fri, Jun 13, 2014 at 7:20 PM, Eric Rubin-Smith wrote:
> If I say sqlite_bind_text(...SQLITE_STATIC), I am promising that the buffer
> is going to stick around for a while. How long am I promising that it will
> stick around? Til the next statement reset()? Til the statement
> finalize()? T
If I say sqlite_bind_text(...SQLITE_STATIC), I am promising that the buffer
is going to stick around for a while. How long am I promising that it will
stick around? Til the next statement reset()? Til the statement
finalize()? Til the database close()?
__
On 13/06/2014 11:04 AM, RSmith wrote:
On 2014/06/13 15:02, Sohail Somani wrote:
My application's architecture looks roughly like this:
- A main thread which does only database reads
- A dedicated database write thread
I needed to create this because while reads are fast, there are
occasions
On 2014/06/13 15:02, Sohail Somani wrote:
My application's architecture looks roughly like this:
- A main thread which does only database reads
- A dedicated database write thread
I needed to create this because while reads are fast, there are occasions where writes take a significant portion
Hi,
My application's architecture looks roughly like this:
- A main thread which does only database reads
- A dedicated database write thread
I needed to create this because while reads are fast, there are
occasions where writes take a significant portion of time and that can
cause the main t
Hi Smith,
Yes it is the internal bluetooth application(bluetooth.apk) comes with the
android Os. from yours suggestion i found that the system exceeded the
total number of open fd(file discriptors) due to that its facing this
problem.
As you have mentioned correctly it is Android Os that is block
On 2014/06/13 09:35, Sathish N wrote:
hi,
Thanks for the help.
As i mentioned i am new to sqlite so i am trying my best.
And this is not my application .its internal application of android. i am
trying to understand and solve this.
once again thanks for the help
Hi Sathish,
Apologies, our
hi,
Thanks for the help.
As i mentioned i am new to sqlite so i am trying my best.
And this is not my application .its internal application of android. i am
trying to understand and solve this.
once again thanks for the help
On Fri, Jun 13, 2014 at 1:00 PM, Igor Korot wrote:
> Hi,
>
> On Fr
Hi,
On Fri, Jun 13, 2014 at 12:24 AM, Sathish N wrote:
> hi Igor Korot,
>
> yes it is happening, every time i update the database. because of this the
> application is getting crashed.
>
> Can you please help me with the solution. As this is the internal apk
> inside the android.
This is you app
hi Igor Korot,
yes it is happening, every time i update the database. because of this the
application is getting crashed.
Can you please help me with the solution. As this is the internal apk
inside the android.
Thanks.
On Fri, Jun 13, 2014 at 12:36 PM, Igor Korot wrote:
> Hi, Satnish,
>
>
Hi, Satnish,
On Fri, Jun 13, 2014 at 12:01 AM, Sathish N wrote:
> hi,
>
> Thanks for the reply.
> what do you mean that i cant write at dest. i am not sure what it means.
It means you are trying to execute an INSERT/UPDATE statement which fails.
It's quite obvious.
Thank you.
>
>
>
>
> On Thu,
hi,
Thanks for the reply.
what do you mean that i cant write at dest. i am not sure what it means.
On Thu, Jun 12, 2014 at 11:55 PM, mm.w <0xcafef...@gmail.com> wrote:
> you can't write at dest, then the journal file fails, quite obvious reading
> the logs
>
>
> On Wed, Jun 11, 2014 at 11:41
23 matches
Mail list logo