Folks,
My C program creates a in-memory database. It creates a table and a unique
index on two columns. If the insert fails due to unique index, it prints old
row and new row. Sometimes it cannot find the old row even though the insert
failed.
Here is the pseudo code:
CreateStmt = “create
Why are you looking for a duplicate with col4 instead of the unique key,
col2, col3 that caused the collision?
On 12/1/2010 7:29 AM, Hemant Shah wrote:
Folks,
My C program creates a in-memory database. It creates a table and a unique
index on two columns. If the insert fails due to unique
Morris jmor...@bearriver.com
Subject: Re: [sqlite] Select fails even though data is in the table.
To: sqlite-users@sqlite.org
Date: Wednesday, December 1, 2010, 9:38 AM
Why are you looking for a duplicate
with col4 instead of the unique key,
col2, col3 that caused the collision?
On 12/1
on behalf of Hemant Shah
Sent: Wed 12/1/2010 10:08 AM
To: General Discussion of SQLite Database
Subject: EXTERNAL:Re: [sqlite] Select fails even though data is in the table.
The unique key is col3 and col4 (SeqNum and MD5Sum).
If the insert fails for this unique key then col4 should be the same
of SQLite Database
Subject: EXTERNAL:Re: [sqlite] Select fails even though data is in the table.
The unique key is col3 and col4 (SeqNum and MD5Sum).
If the insert fails for this unique key then col4 should be the same.
It should find the row for the even if I select for col4 only.
Hemant
...@ngc.com
Subject: Re: [sqlite] Select fails even though data is in the table.
To: General Discussion of SQLite Database sqlite-users@sqlite.org
Date: Wednesday, December 1, 2010, 10:10 AM
The problem is probably in the bind
calls that you are not showing.
If you care to share them we may
-users-boun...@sqlite.org on behalf of Hemant Shah
Sent: Wed 12/1/2010 10:21 AM
To: General Discussion of SQLite Database
Subject: EXTERNAL:Re: [sqlite] Select fails even though data is in the table.
I check for the return code after each bind call and if it is not SQLITE_OK
then I return
--- On Wed, 12/1/10, Jim Morris jmor...@bearriver.com wrote:
From: Jim Morris jmor...@bearriver.com
Subject: Re: [sqlite] Select fails even though data is in the table.
To: sqlite-users@sqlite.org
Date: Wednesday, December 1, 2010, 10:15 AM
If you have another thread running
that deletes
:
From: Jim Morrisjmor...@bearriver.com
Subject: Re: [sqlite] Select fails even though data is in the table.
To: sqlite-users@sqlite.org
Date: Wednesday, December 1, 2010, 10:15 AM
If you have another thread running
that deletes or modifies the table,
then move the commit to after the select
: EXTERNAL:Re: [sqlite] Select fails even though data is in the table.
This is a single thread/process. No other thread or process is accessing the
data.
This is a single process that reads data from message queue and dumps into
database to look for duplicate rows.
The problem occurs for some
{
/* print error message */
}
}
Hemant Shah
E-mail: hj...@yahoo.com
--- On Wed, 12/1/10, Black, Michael (IS) michael.bla...@ngc.com wrote:
From: Black, Michael (IS) michael.bla...@ngc.com
Subject: Re: [sqlite] Select fails even though data is in the table.
To: General Discussion
...@bearriver.com
Subject: Re: [sqlite] Select fails even though data is in the table.
To: sqlite-users@sqlite.org
Date: Wednesday, December 1, 2010, 10:29 AM
I still think you should use the same
columns for searching for the
duplicate that cause the collision. Using
col4 seem problematic. Can
From: sqlite-users-boun...@sqlite.org
on behalf of Hemant Shah
Sent: Wed 12/1/2010 10:24 AM
To: General Discussion of SQLite Database
Subject: EXTERNAL:Re: [sqlite] Select fails even though
data is in the table.
This is a single thread/process. No other thread or process
13 matches
Mail list logo
