Re: [sqlite] Programming API vs console

On 28 Apr 2013, at 9:55am, Igor Korot wrote: > Apologies for noise. > That was an error on my side, which was discovered after spending couple of > hours debugging. No problem. Glad you figured it out. Simon. ___ sqlite-users

Re: [sqlite] Programming API vs console

Apologies for noise. That was an error on my side, which was discovered after spending couple of hours debugging. Thank you all for the help and sorry once again. On Sat, Apr 27, 2013 at 5:20 AM, Simon Slavin wrote: > > On 27 Apr 2013, at 8:34am, Igor Korot

Re: [sqlite] Programming API vs console

On 27 Apr 2013, at 8:34am, Igor Korot wrote: > In the other area of the program I have a transaction that does 5 or 6 > inserts and no selects. > This transaction works fine as I just verified. > > Now in the failing case the flow goes like this: > > First the program

Re: [sqlite] Programming API vs console

Amit, On Sat, Apr 27, 2013 at 1:00 AM, Amit Chaudhuri wrote: > CREATE TABLE playersdrafted(playerid integer, id ineteger, > > Don't think ineteger is what you really mean.:) > Seen it twice now so guessing it's actually in the code > Why you say so? It is a

Re: [sqlite] Programming API vs console

CREATE TABLE playersdrafted(playerid integer, id ineteger, Don't think ineteger is what you really mean.:) Seen it twice now so guessing it's actually in the code On Sat, Apr 27, 2013 at 8:34 AM, Igor Korot wrote: > Simon, > In the other area of the program I have a

Re: [sqlite] Programming API vs console

Simon, In the other area of the program I have a transaction that does 5 or 6 inserts and no selects. This transaction works fine as I just verified. Now in the failing case the flow goes like this: First the program updates couple of tables, then it inserts this particular record. This

Re: [sqlite] Programming API vs console

On 27 Apr 2013, at 8:05am, Igor Korot wrote: > No. Using straight insert with values does not work. > Record still not inserted. Okay, so you now don't have to worry about parameters, or a sub-select or any of those things. What you have identified is that a simple INSERT

Re: [sqlite] Programming API vs console

Simon, On Fri, Apr 26, 2013 at 7:48 PM, Simon Slavin wrote: > > On 27 Apr 2013, at 3:29am, Igor Korot wrote: > > > sqlite> SELECT ownerid FROM owners WHERE ownername = 'Team 1' AND id = 1; > > 53 > > For testing, kill the sub-select in your INSERT

Re: [sqlite] Programming API vs console

On 27 Apr 2013, at 3:29am, Igor Korot wrote: > sqlite> SELECT ownerid FROM owners WHERE ownername = 'Team 1' AND id = 1; > 53 For testing, kill the sub-select in your INSERT command and just put a 53 in there. See if that changes anything. > sqlite> Please retrieve the

Re: [sqlite] Programming API vs console

Simon, On Fri, Apr 26, 2013 at 5:49 PM, Simon Slavin wrote: > > On 27 Apr 2013, at 12:27am, Igor Korot wrote: > > > And here is the log from the console: > > > > SQLite version 3.7.14 2012-09-03 15:42:36 > > Enter ".help" for instructions > > Enter SQL

Re: [sqlite] Programming API vs console

On 27 Apr 2013, at 12:27am, Igor Korot wrote: > And here is the log from the console: > > SQLite version 3.7.14 2012-09-03 15:42:36 > Enter ".help" for instructions > Enter SQL statements terminated with a ";" > sqlite> INSERT INTO playersdrafted VALUES( 125, 1, ( SELECT

Re: [sqlite] Programming API vs console

And here is the log from the console: SQLite version 3.7.14 2012-09-03 15:42:36 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> INSERT INTO playersdrafted VALUES( 125, 1, ( SELECT ownerid FROM owners WHERE ownername = "Team 1" AND id = 1 ), 38, 1, "OF" ); sqlite>

Re: [sqlite] Programming API vs console

Hi, ALL, On Thu, Apr 25, 2013 at 2:41 PM, Random Coder wrote: > On Tue, Apr 23, 2013 at 8:47 PM, Igor Korot wrote: > > > query = wxString::Format(...); > > if( ( result = sqlite3_prepare_v2( m_handle, query, -1, , 0 ) ) != > > SQLITE_OK ) > > > > It's

Re: [sqlite] Programming API vs console

On Tue, Apr 23, 2013 at 8:47 PM, Igor Korot wrote: > query = wxString::Format(...); > if( ( result = sqlite3_prepare_v2( m_handle, query, -1, , 0 ) ) != > SQLITE_OK ) > It's been a while since I've worked with wxWidgets, but when I did, wxString didn't support an implicit

Re: [sqlite] Programming API vs console

Hi, On Thu, Apr 25, 2013 at 1:09 PM, wrote: > Am 2013-04-25 21:43, schrieb Igor Korot: > > Hi, >> >> On Thu, Apr 25, 2013 at 12:31 PM, wrote: >> >> Am 2013-04-25 21:25, schrieb Igor Korot: >>> >>> Simon, >>> On Wed, Apr 24, 2013 at

Re: [sqlite] Programming API vs console

Am 2013-04-25 21:43, schrieb Igor Korot: Hi, On Thu, Apr 25, 2013 at 12:31 PM, wrote: Am 2013-04-25 21:25, schrieb Igor Korot: Simon, On Wed, Apr 24, 2013 at 7:34 PM, Simon Slavin wrote: On 25 Apr 2013, at 3:28am, Igor Korot

Re: [sqlite] Programming API vs console

Hi, On Thu, Apr 25, 2013 at 12:31 PM, wrote: > Am 2013-04-25 21:25, schrieb Igor Korot: > > Simon, >> >> On Wed, Apr 24, 2013 at 7:34 PM, Simon Slavin >> wrote: >> >> >>> On 25 Apr 2013, at 3:28am, Igor Korot wrote: >>> >>> >

Re: [sqlite] Programming API vs console

Am 2013-04-25 21:25, schrieb Igor Korot: Simon, On Wed, Apr 24, 2013 at 7:34 PM, Simon Slavin wrote: On 25 Apr 2013, at 3:28am, Igor Korot wrote: > Changed. No difference at all. Record is still does not show up. My guess is that you are

Re: [sqlite] Programming API vs console

Simon, On Wed, Apr 24, 2013 at 7:34 PM, Simon Slavin wrote: > > On 25 Apr 2013, at 3:28am, Igor Korot wrote: > > > Changed. No difference at all. Record is still does not show up. > > My guess is that you are opening different files in the shell and

Re: [sqlite] Programming API vs console

On 25 Apr 2013, at 3:28am, Igor Korot wrote: > Changed. No difference at all. Record is still does not show up. My guess is that you are opening different files in the shell and your app. This is usually caused by a default file path not being what you think it is. Use

Re: [sqlite] Programming API vs console

Simon, On Wed, Apr 24, 2013 at 5:56 PM, Simon Slavin wrote: > > On 25 Apr 2013, at 1:54am, Igor Korot wrote: > > > Then why this query works in the command prompt console? I don't have > "Team > > 1" column name in any of the tables. > > Nevertheless

Re: [sqlite] Programming API vs console

On 25 Apr 2013, at 1:54am, Igor Korot wrote: > Then why this query works in the command prompt console? I don't have "Team > 1" column name in any of the tables. > Nevertheless I'm going to change this and all other queries that use the > string literals ot use >

Re: [sqlite] Programming API vs console

James, On Wed, Apr 24, 2013 at 4:39 PM, James K. Lowden wrote: > On Wed, 24 Apr 2013 07:20:59 -0500 > "Jay A. Kreibich" wrote: > > > > query = wxString::Format( "INSERT INTO playersdrafted VALUES( %d, % > > > d, ( SELECT ownerid FROM owners WHERE

Re: [sqlite] Programming API vs console

On Wed, 24 Apr 2013 07:20:59 -0500 "Jay A. Kreibich" wrote: > > query = wxString::Format( "INSERT INTO playersdrafted VALUES( %d, % > > d, ( SELECT ownerid FROM owners WHERE ownername = \"%s\" AND id = % > > d ), %d, %d, \"%s\" );", player.GetPlayerId(), leagueId, > > const_cast(

Re: [sqlite] Programming API vs console

On Wed, Apr 24, 2013 at 12:59 PM, Igor Korot wrote: > Clemens, > > On Wed, Apr 24, 2013 at 12:21 PM, Clemens Ladisch wrote: > >> Igor Korot wrote: >> On Wed, Apr 24, 2013 at 12:50 AM, Clemens Ladisch < >> clem...@ladisch.de >> wrote: >> >

Re: [sqlite] Programming API vs console

Clemens, On Wed, Apr 24, 2013 at 12:21 PM, Clemens Ladisch wrote: > Igor Korot wrote: > On Wed, Apr 24, 2013 at 12:50 AM, Clemens Ladisch wrote: > > Igor Korot wrote: > >> ... > >> else > >> sqlite3_step( stmt ); >

Re: [sqlite] Programming API vs console

Igor Korot wrote: On Wed, Apr 24, 2013 at 12:50 AM, Clemens Ladisch Igor Korot wrote: >> ... >> else >> sqlite3_step( stmt ); > > You forgot to check for errors. > I guess the code that executes the COMMIT has the same

Re: [sqlite] Programming API vs console

Hi, ALL, On Wed, Apr 24, 2013 at 11:11 AM, Igor Korot wrote: > > > On Wed, Apr 24, 2013 at 3:54 AM, Clemens Ladisch wrote: > >> Igor Korot wrote: >> > Clement, >> >> Who? ;-) >> > > Oops... > I promise I will never write an E-mail at 1:00 AM ;-) > > >>

Re: [sqlite] Programming API vs console

On Wed, Apr 24, 2013 at 3:54 AM, Clemens Ladisch wrote: > Igor Korot wrote: > > Clement, > > Who? ;-) > Oops... I promise I will never write an E-mail at 1:00 AM ;-) > > On Wed, Apr 24, 2013 at 12:50 AM, Clemens Ladisch >wrote: > >> Igor Korot

Re: [sqlite] Programming API vs console

On 4/24/2013 12:45 AM, Igor Korot wrote: In the beginning I'm issuing "BEGIN". In the end if everything is good I'm issuing "COMMIT", if not "ROLLBACK". So when running under debugger in Visual Studio, right after sqlite3_step() call I am issuing SELECT * FROM playersdrafted in the console. It

Re: [sqlite] Programming API vs console

On Tue, Apr 23, 2013 at 08:47:18PM -0700, Igor Korot scratched on the wall: > Here is the code: > > query = wxString::Format( "INSERT INTO playersdrafted VALUES( %d, %d, ( > SELECT ownerid FROM owners WHERE ownername = \"%s\" AND id = %d ), %d, %d, > \"%s\" );", player.GetPlayerId(), leagueId,

Re: [sqlite] Programming API vs console

On 24 Apr 2013, at 4:47am, Igor Korot wrote: > sqlite3_step( stmt ); > sqlite3_finalize( stmt ); Please check the values SQLite returns from the _step and _finalize calls to make sure it's not generating an error. Simon.

Re: [sqlite] Programming API vs console

Igor Korot wrote: > Clement, Who? ;-) > On Wed, Apr 24, 2013 at 12:50 AM, Clemens Ladisch wrote: >> Igor Korot wrote: >>> ... >>> else >>> sqlite3_step( stmt ); >> >> You forgot to check for errors. >> I guess the code that executes the COMMIT has the same bug. > >

Re: [sqlite] Programming API vs console

Clement, On Wed, Apr 24, 2013 at 12:50 AM, Clemens Ladisch wrote: > Igor Korot wrote: > > ... > > else > > sqlite3_step( stmt ); > > You forgot to check for errors. > I guess the code that executes the COMMIT has the same bug. > I am checking the error. It is from

Re: [sqlite] Programming API vs console

Igor Korot wrote: > ... > else > sqlite3_step( stmt ); You forgot to check for errors. I guess the code that executes the COMMIT has the same bug. Regards, Clemens ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Programming API vs console

Hi, Igor, On Tue, Apr 23, 2013 at 8:55 PM, Igor Tandetnik wrote: > On 4/23/2013 11:47 PM, Igor Korot wrote: > >> During the program flow I need to insert a record in one of the tables >> inside transaction. >> Record inserts OK (no error message generated), but when I try to

Re: [sqlite] Programming API vs console

On 4/23/2013 11:47 PM, Igor Korot wrote: During the program flow I need to insert a record in one of the tables inside transaction. Record inserts OK (no error message generated), but when I try to check using the SQLite console the record is not present. I let the transaction finish and check