Re: [sqlite] sqlite3_column_type returns NOT SQLITE_NULL and the following sqlite3_column_text returns with nullptr

On 9/11/18, heribert wrote: > I've a prepared select statement (the database is in :memory: based.). > After binding the input values, calling next, checking the result type > of a text column, sometimes the follwing sqlite3_column_text returns > with a nullptr. > > The stange thing is: the prior

Re: [sqlite] sqlite3_column_type returns NOT SQLITE_NULL and the following sqlite3_column_text returns with nullptr

Thx Gunter... that's the problem. I've capsuled the sqlite access in some database classes. So i have only the call a function named getProperty with some parameters. But in some cases it may be possible that the instance of the object calls this function from another thread (with the same

[sqlite] sqlite3_column_type returns NOT SQLITE_NULL and the following sqlite3_column_text returns with nullptr

I've a prepared select statement (the database is in :memory: based.). After binding the input values, calling next, checking the result type of a text column, sometimes the follwing sqlite3_column_text returns with a nullptr. The stange thing is: the prior called sqlite3_column_type do not

Re: [sqlite] sqlite3_column_type() returns SQLITE_NULL even though it contains text

On 9/13/17, Stadin, Benjamin wrote: > Hi, > > I was missing a few records in my program. After debugging further, I found > that sqlite3_column_type () returns SQLITE_NULL for some objects (like 10 in > 2000), even though these actually contain text data. > >

[sqlite] sqlite3_column_type() returns SQLITE_NULL even though it contains text

Hi, I was missing a few records in my program. After debugging further, I found that sqlite3_column_type () returns SQLITE_NULL for some objects (like 10 in 2000), even though these actually contain text data. Is this normal? And how should I handle it properly (I mean, check if it’s proper

Re: [sqlite] sqlite3_column_type issue

On 12/17/2010 4:36 AM, Sumedh wrote: > I am using C API > I am using sqlite3_column_type to determine, the type of column as it is > requirement for me to decide whether to return the value as string or > number. It works well, but not in case when i use left outer join. > > When i use left outer

[sqlite] sqlite3_column_type issue

Hi, I am using C API I am using sqlite3_column_type to determine, the type of column as it is requirement for me to decide whether to return the value as string or number. It works well, but not in case when i use left outer join. When i use left outer join, the column type returned is always

Re: [sqlite] sqlite3_column_type bad value

Sebastian Bermudez wrote: > sqlite3_open > sqlite3_prepare ( "select * from t1" ) > get sqlite3_column_count(stmt) > for 1 to colcount > sqlite3_column_type(stmt,index) "always return 5" > next You need to call sqlite3_step first. sqlite3_column_type examines actual data in an actual row,

[sqlite] sqlite3_column_type bad value

i have 1 table: create table t1 ( id integer not null primary key, descri text ) then i exec... "SELECT * FROM t1" when i get the column type... with [ sqlite3_column_type(stmt,index); ] i get always (int)5 = SQLITE_NULL every else is correct !, i have the correct row count, field count;

Re: [sqlite] sqlite3_column_type

On Thu, Feb 14, 2008 at 02:42:16PM -0500, Igor Tandetnik wrote: > Michael Pitchford > <[EMAIL PROTECTED]> wrote: > > I'm having an issue with sqlite3_column_type in the current version > > of sqlite (3.5.6 at the time of this email). Unless I explicitly call > > sqlite3_step() on the statement,

Re: [sqlite] sqlite3_column_type

Michael Pitchford <[EMAIL PROTECTED]> wrote: > I'm having an issue with sqlite3_column_type in the current version > of sqlite (3.5.6 at the time of this email). Unless I explicitly call > sqlite3_step() on the statement, it returns SQLITE_NULL for every > column. Is this a bug or is it just how

[sqlite] sqlite3_column_type

Hello All, I'm having an issue with sqlite3_column_type in the current version of sqlite (3.5.6 at the time of this email). Unless I explicitly call sqlite3_step() on the statement, it returns SQLITE_NULL for every column. Is this a bug or is it just how the sqlite3_column_type works now?