Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On Fri, Nov 30, 2018 at 3:15 PM Dominique Devienne wrote: > sqlite> .header on > sqlite> create table t (c, n); > sqlite> insert into t values (1, 'one'), (2, 'two'), (3, 'three'); > sqlite> select n from t where c in (select value from json_each('[1, 3]')); > n > one > three Very nice! Now I c

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On Fri, 30 Nov 2018 23:25:48 +0900 Simon Walter wrote: > > SELECT id, data FROM val WHERE id IN ("1, 893, 121212"); ... > I have no idea yet if MySQL and/or PostgreSQL can handle this > scenario and how they do it. The important thing to understand about parameterized queries is that they are n

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On Fri, Nov 30, 2018 at 3:26 PM Simon Walter wrote: > On 11/30/2018 11:20 PM, Dominique Devienne wrote: > To be honest, I am using apr_dbd as I would like to support more than > just SQLite. So I will need to play around with MySQL and PostgreSQL at > least and maybe branch if SQLite is in use. I

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On 11/30/2018 11:20 PM, Dominique Devienne wrote: > On Fri, Nov 30, 2018 at 3:03 PM Dominique Devienne > wrote: > >> On Fri, Nov 30, 2018 at 2:44 PM Richard Hipp wrote: >> >>> On 11/30/18, Simon Walter wrote: Thanks Dominique, Much appreciated. I can now stop pulling out my hair.

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On 2018/11/30 2:52 PM, Simon Walter wrote: I am trying to make a prepared statement that has a parameter such as "1, 893, 121212". obviously it is text (a string) but it cannot be quoted or the result will be: SELECT id, data FROM val WHERE id IN ("1, 893, 121212"); I understand normally I would

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On Fri, Nov 30, 2018 at 3:03 PM Dominique Devienne wrote: > On Fri, Nov 30, 2018 at 2:44 PM Richard Hipp wrote: > >> On 11/30/18, Simon Walter wrote: >> > Thanks Dominique, >> > >> > Much appreciated. I can now stop pulling out my hair. I will do >> > something with sprintf. >> >> See https://w

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On Fri, Nov 30, 2018 at 2:44 PM Richard Hipp wrote: > On 11/30/18, Simon Walter wrote: > > Thanks Dominique, > > > > Much appreciated. I can now stop pulling out my hair. I will do > > something with sprintf. > > See https://www.sqlite.org/carray.html Right. Any table-valued function would do

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On 11/30/18, Simon Walter wrote: > Thanks Dominique, > > Much appreciated. I can now stop pulling out my hair. I will do > something with sprintf. See https://www.sqlite.org/carray.html Or, failing that, at least use sqlite3_mprintf() rather than sprintf(). https://www.sqlite.org/printf.html -

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

Thanks Dominique, Much appreciated. I can now stop pulling out my hair. I will do something with sprintf. Best regards, Simon On 11/30/2018 10:37 PM, Dominique Devienne wrote: > On Fri, Nov 30, 2018 at 2:10 PM Simon Walter wrote: > >> How does one use WHERE x IN (?) with a prepared statement?

Re: [sqlite] sqlite3_bind_text() and WHERE x IN (?)

On Fri, Nov 30, 2018 at 2:10 PM Simon Walter wrote: > How does one use WHERE x IN (?) with a prepared statement? What is the > correct way to do this? > You cannot do it. Must use WHERE x IN (?, ?, ?), i.e. an explicit and known in advance number of bind placeholders. Or not use binding at all,

[sqlite] sqlite3_bind_text() and WHERE x IN (?)

I am trying to make a prepared statement that has a parameter such as "1, 893, 121212". obviously it is text (a string) but it cannot be quoted or the result will be: SELECT id, data FROM val WHERE id IN ("1, 893, 121212"); I understand normally I would need the quotes, such as: SELECT id, name, v

[sqlite] sqlite3_bind_text with empty sting....

I have a table with a not null column... Some of the values are empty string and some have more lengthy values :-) I prepare a statement ("Select col2 from table where column = ?") and then use bind to that parameter what are the parameters ? From slq browser I can "Select col2 from tab

Re: [sqlite] sqlite3_bind_text and strings that look like numbers

Simon Slavin wrote on Tuesday, January 06, 2015 3:00 PM > > On 6 Jan 2015, at 7:49pm, Nelson, Erik - 2 > wrote: > > > Is there any way to force the bind_text() to store the input text > verbatim? > > Another possibility is that everything is being stored fine, and that > something is changing t

Re: [sqlite] sqlite3_bind_text and strings that look like numbers

Richard Hipp wrote Tuesday, January 06, 2015 3:04 PM > On 1/6/15, Nelson, Erik - 2 wrote: > > > > converts the value to a textual scientific notation representation, > > like > > Nope. SQLite is not doing this. Something else is going on. > > sqlite3_bind_text() does not do conversions when in

Re: [sqlite] sqlite3_bind_text and strings that look like numbers

On 1/6/15, Nelson, Erik - 2 wrote: > This is part of a larger application, but what I *think* is happening is > using a table definition like > > create table tester(id text collate nocase) > > and a prepared statement like > > insert into tester values(?) > > then calling bind something like this

Re: [sqlite] sqlite3_bind_text and strings that look like numbers

On 6 Jan 2015, at 7:49pm, Nelson, Erik - 2 wrote: > Is there any way to force the bind_text() to store the input text verbatim? "A column with TEXT affinity stores all data using storage classes NULL, TEXT or BLOB. If numerical data is inserted into a

[sqlite] sqlite3_bind_text and strings that look like numbers

This is part of a larger application, but what I *think* is happening is using a table definition like create table tester(id text collate nocase) and a prepared statement like insert into tester values(?) then calling bind something like this pseudocode sqlite3_bind_text(stmt, column, "1

Re: [sqlite] sqlite3_bind_text issue

>-Ursprüngliche Nachricht- >Von: lyx [mailto:sdu...@163.com] >Gesendet: Montag, 05. Mai 2014 05:00 >An: sqlite-users@sqlite.org >Betreff: Re: [sqlite] sqlite3_bind_text issue > >I have tried to use SQL_TRANSIENT instead of SQLITE_STATIC in >sqlite3_bind_text. But

Re: [sqlite] sqlite3_bind_text issue

A Dilluns, 5 de maig de 2014 02:59:59, lyx va escriure: > I have tried to use SQL_TRANSIENT instead of SQLITE_STATIC in > sqlite3_bind_text. But the result is still not correct. The column num is > correct now but the row number embedded in column data in every row is all > assigned to zero now. It

Re: [sqlite] sqlite3_bind_text issue

change SQLITE_STATIC to SQLITE_TRANSIENT 2014-05-04 smartenc 发件人：lyx 发送时间：2014-05-04 13:11 主题：[sqlite] sqlite3_bind_text issue 收件人："sqlite-users" 抄送： Hi Experts, I'm trying to use sqlite3_bind_text in my database insert procedure using sqlite 3.8.4.3. I have a very simpl

Re: [sqlite] sqlite3_bind_text issue

e From: lyx Date: 04/05/2014 06:11 (GMT+00:00) To: sqlite-users@sqlite.org Subject: [sqlite] sqlite3_bind_text issue Hi Experts, I'm trying to use sqlite3_bind_text in my database insert procedure using sqlite 3.8.4.3. I have a very simple table and the '.schema'

[sqlite] sqlite3_bind_text issue

Hi Experts, I'm trying to use sqlite3_bind_text in my database insert procedure using sqlite 3.8.4.3. I have a very simple table and the '.schema' output is as following: sqlite> .schema CREATE TABLE ins_test(col1 text, col2 text, col3 text, col4 text, col5 text, col6 text); CREATE INDEX id

Re: [sqlite] sqlite3_bind_text truncates strings with "."

Hello Nickye, I insert strings with "." all the time. In fact I'd say most insertions I do have "."s in them so, I don't think there's an inherent problem in Sqlite. I convert everything to UTF8 before I insert though the UTF8 of "." is ".". C Monday, July 15, 2013, 3:13:4

Re: [sqlite] sqlite3_bind_text truncates strings with "."

On 7/15/2013 3:13 PM, nic...@mail.ru wrote: Prepared statement SQL: "INSERT INTO tbl VALUES(?1);" Column type:TEXT String to bind (ASCII, zero terminated): "abcd.ef" nBytes parameter: -1 destructor parameter: SQLITE_STATIC Result after call sqlite3_step: "abcd" Works for me. There's must be

[sqlite] sqlite3_bind_text truncates strings with "."

Hello, Prepared statement SQL: "INSERT INTO tbl VALUES(?1);" Column type:TEXT String to bind (ASCII, zero terminated): "abcd.ef" nBytes parameter: -1 destructor parameter: SQLITE_STATIC Result after call sqlite3_step: "abcd" With nBytes==(len(String)) there's no problem, res

Re: [sqlite] sqlite3_bind_text destructor

QLite Database Subject: Re: [sqlite] sqlite3_bind_text destructor Stephan Beal wrote, On 1/25/2012 11:36 AM: > On Wed, Jan 25, 2012 at 6:33 PM, Bill McCormickwrote: > >> http://www.sqlite.org/**capi3ref.html#sqlite3_bind_**blob<http://www. >> sqlite.org/capi3ref.html#sqlite3_bi

Re: [sqlite] sqlite3_bind_text and SQLITE_STATIC

> I'd expect that after sqlite3_step is done I can safely change > that buffers, but it seems not. > Is it a bug? Feature or incorrect use of SQLITE_STATIC It's an incorrect use of SQLITE_STATIC. Only call to sqlite3_finalize() can guarantee you that buffer won't be used again. Probably a pair of

[sqlite] sqlite3_bind_text and SQLITE_STATIC

Hello, One of the things that is useful is sqlite3_bind_text is SQLITE_STATIC that allows to reduce memory copy. I assumed that I need to keep the value valid until I execute that statement, however I discovered it does not work this way: Following simple program prints "xbcd" instead of expected

Re: [sqlite] sqlite3_bind_text data conversion

Hello, Simon. You wrote Thursday, January 26, 2012, 07:37:19: >> rez = sqlite3_exec(ss_pdb, "CREATE TABLE T(str STRING, val INTEGER);", NULL, >> NULL, NULL); > > Datatypes in SQLite are as follows: > > http://www.sqlite.org/datatype3.html > > Your word 'STRING' is being interpreted as a numeric

Re: [sqlite] sqlite3_bind_text data conversion

On 26 Jan 2012, at 12:15pm, darkelf wrote: > rez = sqlite3_exec(ss_pdb, "CREATE TABLE T(str STRING, val INTEGER);", NULL, > NULL, NULL); Datatypes in SQLite are as follows: http://www.sqlite.org/datatype3.html Your word 'STRING' is being interpreted as a numeric affinity. And as the value y

[sqlite] sqlite3_bind_text data conversion

Hello, all. Could anybody clarify to me data conversion done in sqlite3_bind_text(), please? I've written simple test: test.c ;--X8 #include #include "sqlite3.h" int main(int argc, char* argv[]) { int rez = 0; sqlite3* ss_pdb = NULL; sqlite3_stmt* st; rez =

Re: [sqlite] sqlite3_bind_text destructor

Stephan Beal wrote, On 1/25/2012 11:36 AM: On Wed, Jan 25, 2012 at 6:33 PM, Bill McCormickwrote: http://www.sqlite.org/**capi3ref.html#sqlite3_bind_**blob Ha! That's the full description that left me with my questions in the first place!!

Re: [sqlite] sqlite3_bind_text destructor

On Wed, Jan 25, 2012 at 6:33 PM, Bill McCormick wrote: > http://www.sqlite.org/**capi3ref.html#sqlite3_bind_**blob >> > Ha! That's the full description that left me with my questions in the > first place!! Lol! Fair enough. > http://www.ad

Re: [sqlite] sqlite3_bind_text destructor

Stephan Beal wrote, On 1/25/2012 11:01 AM: On Wed, Jan 25, 2012 at 5:45 PM, Bill McCormickwrote: 2. What will be void* argument be to the destructor? 3. What void* should the destructor return? int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*)); It doesn't return

Re: [sqlite] sqlite3_bind_text destructor

On Wed, Jan 25, 2012 at 5:45 PM, Bill McCormick wrote: > 2. What will be void* argument be to the destructor? > 3. What void* should the destructor return? > int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*)); It doesn't return a (void *) - it returns void. The (*) i

[sqlite] sqlite3_bind_text destructor

The documentation I see for the sqlite3_bind_text 5th argument (a destructor used to dispose of the BLOB or string after SQLite has finished with it) isn't clear: 1. I assume the "string" that we're talking about here is the 3rd argument (const char*) 2. What will be void* argument be to the

Re: [sqlite] sqlite3_bind_text(): unable to insert "const char*" data into the database.

On 01/04/2012 05:02 PM, Phong Cao wrote: Hello everybody, I am trying to develop a small music manager using Gtkmm, GStreamermm& SQLite3 in Linux (Fedora 16 - 64bit). It is able to read metadata (track, title, artist, album, etc...) of all the files using GStreamermm& inserts these metadata int

[sqlite] sqlite3_bind_text(): unable to insert "const char*" data into the database.

Hello everybody, I am trying to develop a small music manager using Gtkmm, GStreamermm & SQLite3 in Linux (Fedora 16 - 64bit). It is able to read metadata (track, title, artist, album, etc...) of all the files using GStreamermm & inserts these metadata into the underlying SQLite database. Then it

Re: [sqlite] sqlite3_bind_text problem

Matthew Allen <[EMAIL PROTECTED]> writes: > There may be another variable that I didn't mention in my first post, and that is I'm compiling sqlite using > Visual C++ 6 on windows atm and maybe there is a problem that only shows up in VC6 and not in gcc. So with that in > mind I'm building the Mac

Re: [sqlite] sqlite3_bind_text problem

-- Original Message -- To: (sqlite-users@sqlite.org) From: Igor Tandetnik ([EMAIL PROTECTED]) Subject: Re: [sqlite] sqlite3_bind_text problem Date: 17/11/2008 11:58:18a > Despite what the indentation might suggest, the "else" clause at (3) > corresponds to the &

Re: [sqlite] sqlite3_bind_text problem

"Matthew Allen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > http://www.memecode.com/temp/Sqlite_Test.zip [921kb] #define SERIALIZE_STR(Var, Col) \ if (Write) \ { \ (1) if (Var) \ (2) if (!Check(sqlite3_bind_text(Stmt, Col+1, (const char*)Var, -1, SQLITE_STATIC))) \ retu

Re: [sqlite] sqlite3_bind_text problem

-- Original Message -- To: (sqlite-users@sqlite.org) From: Igor Tandetnik ([EMAIL PROTECTED]) Subject: Re: [sqlite] sqlite3_bind_text problem Date: 14/11/2008 11:47:54p > > And it return SQLITE_OK, however the value in the DB is NULL, or an > > empty string. > &g

Re: [sqlite] sqlite3_bind_text problem

> I'm compiling sqlite using Visual C++ 6 on windows atm and maybe there is a > problem that only shows up in VC6 and not in gcc. So with that in mind I'm > building the Mac port of my software (which is built using gcc) and try to > reproduce the problem there. I guess if everything is perfect

Re: [sqlite] sqlite3_bind_text problem

> > And it return SQLITE_OK, however the value in the DB is NULL, or an > > empty string. > > How do you determine this? I open the sqlite db in Sqlite database browser and the field is empty. All the other int fields are there and correct. > I don't see any obvious problems in the code you've

Re: [sqlite] sqlite3_bind_text problem

-- Original Message -- To: General Discussion of SQLite Database (sqlite-users@sqlite.org) From: Eric Minbiole ([EMAIL PROTECTED]) Subject: Re: [sqlite] sqlite3_bind_text problem Date: 15/11/2008 12:22:53a > > Then a bind the values to that statement and write it to the DB

Re: [sqlite] sqlite3_bind_text problem

> Then a bind the values to that statement and write it to the DB. That all > works except for the TEXT field "Name". I'm calling sqlite3_bind_text like > this: > > char *Name = "Something"; > sqlite3_bind_text(Stmt, 3, (const char*)Name, -1, SQLITE_STATIC); > > And it return

Re: [sqlite] sqlite3_bind_text problem

"Matthew Allen" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I have a table with the following fields: > > {"Id", "INTEGER PRIMARY KEY AUTOINCREMENT"}, > {"ParentId", "INTEGER"}, > {"Name", "TEXT"}, > {"Unread", "INTEGER"}, > {"Open", "INTEGER"}, > {"ItemType", "INTEGER"}, > {"Sort

[sqlite] sqlite3_bind_text problem

I have a table with the following fields: {"Id", "INTEGER PRIMARY KEY AUTOINCREMENT"}, {"ParentId","INTEGER"}, {"Name","TEXT"}, {"Unread", "INTEGER"}, {"Open","INTEGER"}, {"Ite

Re: [sqlite] sqlite3_bind_text

yes.. i get it... the thing is that my str is more like str[][] = {"1,2","2,5,6","2,3,6,7,8","1,2,9"}; so i think i'm staying with for (i=0;i: You could also do this Query = sqlite3_mprintf("select name from foo where id = ?"); rc = sqlite3_prepare_v2(DB,Query ,-1,&Statement,NULL); char st

Re: [sqlite] sqlite3_bind_text

You could also do this Query = sqlite3_mprintf("select name from foo where id = ?"); rc = sqlite3_prepare_v2(DB,Query ,-1,&Statement,NULL); char str[20][5] = {"32","2","66","3","88"} ; for (i=1;str[i]; i ++) { sqlite3_reset(&Statement) ; sqlite3_bind_text(Statement,1,str[i],-1,NULL);

Re: [sqlite] sqlite3_bind_text

You can not provide in list items using bind as you described However you can do this: Query = sqlite3_mprintf("select name from foo where id in (%s, %s, %s, %s, %s)", str1, str2, str3, str4, str5); rc = sqlite3_prepare_v2(DB,Query ,-1,&Statement,NULL); Then step through the query r

[sqlite] sqlite3_bind_text

I'm not quite sure if what i'm doing is correct. i have a table with id's and names.. table foo{ id INTEGER PRIMARY KEY, name varchar } then, i have to get all the names of a group (variable length) of elements in foo(i have the id's in ONE string) so i did this. Query = sql

[sqlite] sqlite3_bind_text

Hi, In the following API, sqlite3_bind_text(pStmt, 1, "sample", -1, SQLITE_STATIC); What does the second argument referes to?If the no.of binding arguments are more than one whether we have to mention two. Can you please explain the usage of second argument.I didn't get properly from the documentat

Re: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

Greg Miller wrote: > Thomas Briggs wrote: > >> >> >>> From the looks of this warning, I would guess that you could redefine >>> SQLITE_STATIC like this (or some variation of this that is legal C++) >>> to solve >>> the problem: >>> >>> #define SQLITE_STATIC ((extern "C" void(*)(void*)) 0) what

Re: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

Thomas Briggs wrote: From the looks of this warning, I would guess that you could redefine SQLITE_STATIC like this (or some variation of this that is legal C++) to solve the problem: #define SQLITE_STATIC ((extern "C" void(*)(void*)) 0) I don't think there's any legal way to do this, is t

Re: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

On 4/27/05, Thomas Briggs <[EMAIL PROTECTED]> wrote: > > > From the looks of this warning, I would guess that you could redefine > > SQLITE_STATIC like this (or some variation of this that is > > legal C++) to solve > > the problem: > > > > #define SQLITE_STATIC ((extern "C" void(*)(void*)) 0) >

RE: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

> From the looks of this warning, I would guess that you could redefine > SQLITE_STATIC like this (or some variation of this that is > legal C++) to solve > the problem: > > #define SQLITE_STATIC ((extern "C" void(*)(void*)) 0) I don't think there's any legal way to do this, is there? Li

Re: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

"Gerry Blanchette" <[EMAIL PROTECTED]> writes: > Clearly, the C++ compiler is substituting SQLITE_STATIC with ((void(*)(void > *))0), as the warning from the Solaris C++ compiler claims: > > Warning (Anachronism): Formal argument 5 of type extern "C" void(*)(void*) in > call to sqlite3_bind_text

RE: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

ng way to sidestep this issue, what is typically done to placate this warning? Thanks again, -- Gerry Blanchette -Original Message- From: Gé Weijers [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 27, 2005 1:09 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] sqlite3_bind_text()

Re: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

Ulrik Petersen wrote: > Hi Gerry, > > Gerry Blanchette wrote: > >> Greetings All, >> In general, is passing NULL to sqlite3_bind_text() as parameter 5 valid, >> instead of using either SQLITE_STATIC or SQLITE_TRANSIENT? (My bind >> value is a heap pointer which I manage). >> >> I ask because on S

Re: [sqlite] sqlite3_bind_text() and SQLITE_STATIC question

Hi Gerry, Gerry Blanchette wrote: Greetings All, In general, is passing NULL to sqlite3_bind_text() as parameter 5 valid, instead of using either SQLITE_STATIC or SQLITE_TRANSIENT? (My bind value is a heap pointer which I manage). I ask because on SOLARIS, compiling (C++ compiler, .cpp module) wh

[sqlite] sqlite3_bind_text() and SQLITE_STATIC question

Greetings All, In general, is passing NULL to sqlite3_bind_text() as parameter 5 valid, instead of using either SQLITE_STATIC or SQLITE_TRANSIENT? (My bind value is a heap pointer which I manage). I ask because on SOLARIS, compiling (C++ compiler, .cpp module) when passing SQLITE_STATIC produces