Hi Ben,
You said: "You will notice
that for certain queries, xBestIndex/xFilter does not get
used. That means that the SQLite engine is going to have to
walk through your entire table, evaluating the conditions on
each field."
I am not aware of this behavior. Could you cite an example?
I
If you are talking about the sqlite3 shell, add -interactive to the command
line.
Cheers,
Mark
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Derrell Lipman
> Sent: Wednesday, April 02, 2008 9:36 AM
> To: General Discussion of SQLite Database
>
...snip...
>
> LIKE operators cannot use indices unless the index is case
> insensitive. Use GLOB for case sensitive fields.
>
Richard - i'm not sure i understand "unless the index is case insensitive."
How does that relate to:
sqlite> create table t (a varchar(10) primary key, b, c);
sqlite>
SQLite experts:
The xBestIndex method of the SQLite virtual table interface implemented by the
VT module returns an output to the core by setting idxNum member var of struct
sqlite3_index_info to a value that is meaningful to the VT module. Assume that
a memory resource was created in
I tracked down the cause of this problem to an experimental change made locally
to SQLite. :-(
All is well with SQLite! :-)
Mark
> -Original Message-
> From: Evans, Mark (Tandem)
> Sent: Friday, January 18, 2008 3:45 PM
> To: sqlite-users@sqlite.org
> Subject: [sq
Doh! Wrong thread. :) :) :)
> -Original Message-
> From: Zbigniew Baniewski [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 18, 2008 5:14 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] SQLite character comparisons
>
> On Fri, Jan 18, 2008 at 11:04:09
Think of NULL as "value is unknown".
With zero length blob/text, value is known: 0-length blob/text
Cheers,
Mark
> -Original Message-
> From: Zbigniew Baniewski [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 18, 2008 4:51 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite]
Hi all,
SQLite version 3.5.3 - with custom virtual table module.
I am having a problem with assertion failure following processing of an INSERT
statement relative to a virtual table. Everything works through the call for
VUpdate, then it asserts in vdbe.o in leg for Dup. I'm wondering if
, DELETE, etc.
>
> See also sqlite3_sql() if sqlite3_prepare_v2() or
> sqlite3_prepare16_v2() was used.
>
> http://www.sqlite.org/cvstrac/chngview?cn=4543
>
> --- Igor Tandetnik <[EMAIL PROTECTED]> wrote:
> > Evans, Mark (Tandem) <[EMAIL PROTECTED]> wrote:
> &
Greetings lite-meisters,
Would I be the first person to wish there were a way for, say, a JDBC driver
that uses SQLite to be able to tell what kind of SQL statement it is executing?
Unless I missed an API, sqlite3_step() indicates either a SELECT that matched
at least one row, or any
Just visited the new front page. I like it a lot.
But one of the crown jewel features (at least to me) is buried in the
fine print: Virtual Tables. Is this an oversight? I would at least
put a blurb on the Features or Distinctive Features page unless there's
a motivation not to do so
I like 3 too. There's a minor glitch on Firefox - increasing font size
causes the right side of menu bar to be whited out but display when
cursor hovers. Is this the bug Joe refers to below?
Mark
> -Original Message-
> From: Joe Wilson [mailto:[EMAIL PROTECTED]
> Sent: Friday, November
I love the website. Suggested improvements:
- link to the users site from home:
http://www.mail-archive.com/sqlite-users@sqlite.org/info.html
- a publicity page that contains links to interviews, reviews, etc.
- expand the list of things that cannot be done with virtual tables (it
lists triggers
Thanks Andy
> -Original Message-
> From: Andrew McDermott [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 07, 2007 7:47 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] How should virtual table module return
> its own error messages?
>
>
> Hi,
>
> > Greetings,
> >
> >
To answer my own question:
The magic is in either
SQLITE_CASE_SENSITIVE_LIKE
compile time option or
CASE_SENSITIVE_LIKE pragma.
I have seen this before, but it just didn't stick in my small memory
bank.
Mark
> -Original Message-
> From: Evans, Mark (Tandem)
> Sen
Hi all,
In a virtual table context, I expected a statement such as
select * from t where x like 'abc%'
to pass a constraint for the LIKE clause to xBestIndex method of virtual
table module but it doesn't get such a constraint. I expected
SQLITE_INDEX_CONSTRAINT_MATCH. Do I have to do
Mark
> -Original Message-
> From: Evans, Mark (Tandem)
> Sent: Sunday, November 04, 2007 7:12 AM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] How many virtual table implemenations
> are there out there?
>
> I would like to second the suggestion of Ralf and add
I would like to second the suggestion of Ralf and add a couple
of my own:
1) Modify xOpen interface to:
int ndmOpen(sqlite3_vtab *pVTab, sqlite3_vtab_cursor **ppCursor, int
update) ;
where 'update' is an additional argument that indicates whether the
context is
for read-only select (0), or
I would like a virtual table cursor to distinguish read-only access
(SELECT statement/clause) from searched UPDATE/DELETE access.
For UPDATE / DELETE, I want to lock *my* rows in xNext cursor operation.
Is there a way to distinguish or is this a dumb question?
Many thanks
Mark
Hi all,
It's nit-picking time...
I'm writing a virtual table module and ran into a little gotcha. The
INSERT syntax allows one to specify NULL as a column value or to omit a
column name. Compare:
insert into T(a,c) values (1,2) take default value for
column B if any
versus
Thanks Dan
> -Original Message-
> From: Dan Kennedy [mailto:[EMAIL PROTECTED]
> Sent: Sunday, October 28, 2007 11:11 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Virtual table xFilter argv object longevity
>
> On Sun, 2007-10-28 at 14:03 +, Evans
The question is what is the lifetime of sqlite3_value objects passed as
argv array to the xFilter virtual table module call? Can I save the
pointers and reference the values for constraint testing in my
implementation of xNext? Fingers crossed.
Many thanks,
Mark
Hi All,
I am exploring the use of the Virtual Table capability of SQLite 3.5.1
for implementing alternative backing store and have a couple of
questions for virtual table gurus:
Say I define a virtual table module registered as "custom" and then
define virtual table T as follows:
CREATE VIRTUAL
Thanks Joe
> -Original Message-
> From: Joe Wilson [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 08, 2007 1:45 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] 3.5.1 build issues
>
> "make test" already fixed in CVS.
>
> http://www.sqlite.org/cvstrac/tktview?tn=2689
>
Addendum: There is a new file, src/test_onefile.c, that needs to be
added to Makefile.in.
-Original Message-
From: Evans, Mark (Tandem)
Sent: Monday, October 08, 2007 12:23 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] 3.5.1 build issues
A glitch or two got introduced into the 3.5.1
I am building sqlite 3.5.0 using x-dev tools for HP NonStop OSS target
machine and am working through some issues. One of the issues is a
compiler error that results from a literal, SQLITE_BIG_DBL, used in
src/where.c. That literal is defined in sqliteInt.h as (1e99) which is
bigger than the
It's hard to drag my Linux server to Starbucks. :-)
Next Windows laptop, though, will definitely have to have a
Linux/Windows dual personality. I'll have to wait until the next
mega-merger for a Mac.
Mark
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>
memory usage: 76060 bytes
So it looks like I have a cygwin TCL issue. Is this fixable?
Mark
> -Original Message-
> From: Evans, Mark (Tandem)
> Sent: Friday, September 21, 2007 5:47 PM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] test failures on cygwin
>
>
Hi all,
I have been lurking on the message board and am in awe of the collective
wisdom.
I'm just getting my feet wet learning the internals of SQLite, drinking
from the proverbial firehose. I am using cygwin 1.90 as my learning
platform and I have built SQLite 3.5.0. I ran 'make test'
29 matches
Mail list logo
