Hi,
create table test (t text);
insert into test values ('9');
insert into test values ('98');
insert into test values ('986');
insert into test values ('9867');
select * from test where '98555' like t || '%' order by t desc limit 1;
When we try to compile the above sql as a statement,we get Success but
when we bind it gives a error "SQLITE_RANGE".
After inspection we find
"sParse.nVar" = 0 [which represent nr of "?"]
Can u pls help to correct this error.
regards
ragha
******************************************************************************************
This email and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive this
e-mail in error, please notify the sender by phone or email immediately and
delete it!
*****************************************************************************************
----- Original Message -----
From: Daniel Önnerby <[EMAIL PROTECTED]>
Date: Wednesday, August 29, 2007 4:20 pm
Subject: Re: [sqlite] Towards SQLite version 3.5.0
> Hi!
>
> The new multithread-features will be great.
> Do you think that it will be better to share one connection
> between all
> theads in an application or is better to have each thread open a
> new
> connection and use the sqlite3_enable_shared_cache?
>
> Best regards
> Daniel
>
> [EMAIL PROTECTED] wrote:
> > The transition from 3.4.2 to 3.5.0 will perhaps be the
> > largest single change to SQLite since 2.8->3.0. There
> > will not be that many visible changes, but a lot is
> > changing behind the scenes. Some less frequently used
> > interfaces will be changing in slightly incompatible
> > ways. Users who have build customized OS intereface layers
> > or backends for SQLite will find that they are going to
> > need to do some rework.
> >
> > SQLite version 3.5.0 is not close to being ready yet.
> > But it is to the point where the source code will
> > compile and pass many tests. And so I would like to
> > take this opportunity to encourage people in the
> > community to download the CVS HEAD and give it
> > a whirl in their applications. Please let me know
> > about any serious issues you run across.
> >
> > I have *started* to prepare documentation describing
> > the changes in 3.5.0. This is draft documentation.
> > But for those who are interested, please visit
> >
> > http://www.sqlite.org/34to35.html
> > http://www.sqlite.org/capi350ref.html
> >
> > In particular, if your application uses a customized
> > OS interface for SQLite, you should read the 34to35.html
> > document to see exactly what will be involved in porting
> > your application to run with version 3.5.0.
> >
> > The SQLite code currently in CVS HEAD is not ready for
> > production use. We know that. We know what many of the
> > problems are and Dan and I are working long hours to fix
> > them. It's the problems that we *do not* know about that
> > are scary. So that is why I am inviting the larger
> > community to have an early look and perhaps bring our
> > attention to issues sooner rather than later.
> >
> > --
> > D. Richard Hipp <[EMAIL PROTECTED]>
> >
> >
> > -----------------------------------------------------------------
> ------------
> > To unsubscribe, send email to [EMAIL PROTECTED]
> > -----------------------------------------------------------------
> ------------
> >
> >
>
>
> -------------------------------------------------------------------
> ----------
> To unsubscribe, send email to [EMAIL PROTECTED]
> -------------------------------------------------------------------
> ----------
>
>
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
