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
--- "Evans, Mark (Tandem)" <[EMAIL PROTECTED]> wrote:
> 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 update (1),
(). This is a show-stopper
for VT implementations that allow NULL for unkown column values.
Warm regards,
Mark
> -Original Message-
> From: Ralf Junker [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 02, 2007 7:38 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] How man
Hi Darren,
On 11/3/07, Darren Duncan <[EMAIL PROTECTED]> wrote:
> At 9:42 AM -0400 11/2/07, Samuel R. Neff wrote:
> I think the real problem here is "virtual" is a broad enough term ...
I immediately think about MySQL when you use terms like "federated"
and "data engine". With the word
At 9:42 AM -0400 11/2/07, Samuel R. Neff wrote:
I like the term virtual 'cause that's exactly what they are.. a table that
does not really exist in the db and is provided by some other system. This
is not inconsistent with other DBMS's which use terms like "virtualized
view", both are tables
Terms like "foreign" and "federated" conjure up images of physical
tables that reside in external databases, which is not at all what
this feature is. It's simply an interface that looks like a table.
-
To unsubscribe,
Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 01, 2007 5:33 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How many virtual table implemenations are there out
there?
I agree.
>But to do so seems likely to require an incompatible change to the
>virtual-table interface.
Could I kindly request an addition to the incompatible change to the
virtual-table interface?
I would very much appreciate a corresponding function to
function xRowID(
pCursor:
I agree.
How about "Synthetic Table" or "Abstract Table"?
--- Darren Duncan <[EMAIL PROTECTED]> wrote:
> While you're at it, I strongly recommend changing the feature name
> from "virtual table" to "federated table", or at least not something
> called "virtual", because the older/current name
At 9:03 AM -0400 11/1/07, D. Richard Hipp wrote:
The current virtual-table implementation does not work when you have
shared cache mode enabled. We would like to fix this so that that you can
(for example) use FTS and shared cache at the same time. But to do so
seems likely to require an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
> The current virtual-table implementation does not work when you have
> shared cache mode enabled.
Can you also fix the xFindFunction api? The problem with it is that I
have no idea when SQLite is finished with the function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
> If you have or know of a virtual table implementation (other than the ones
> that are included with SQLite - such as FTS1-3) that will be broken by an
> API change, please let me know. And please also advice me how much of
>
To make virtual tables compatible with shared cache would be a
convenience for us, and not in the least inconvenient.
D. Richard Hipp wrote:
The current virtual-table implementation does not work when you have
shared cache mode enabled. We would like to fix this so that that you can
(for
Hello,
> The current virtual-table implementation does not work when you have
> shared cache mode enabled. We would like to fix this so that that
> you can (for example) use FTS and shared cache at the same time.
> But to do so seems likely to require an incompatible change to the
>
The current virtual-table implementation does not work when you have
shared cache mode enabled. We would like to fix this so that that
you can
(for example) use FTS and shared cache at the same time. But to do so
seems likely to require an incompatible change to the virtual-table
15 matches
Mail list logo
