A reversed-string index, which would be used transparently on ends-with
queries, would not have to store the data redundantly in the base table.
That is what I think you are suggesting?Though I would welcome the "smart"
approach you suggest, it is far more ambitious than a raw-reverse function.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2010 08:00 AM, Tim Romano wrote:
> Several things might be responsible for there being no "outpouring of
> support" for a raw reverse function.
Also note that you are proposing it as a very specific workaround for a
specific scenario which
Roger,
I'm not thinking of you as a gatekeeper but as a member of the "vocal
opposition". You did oppose my request, after all, you didn't simply
ignore it. But your opposition was not unreasonable -- it was simply based
on certain assumptions that I saw an opportunity to address.
Several
2010/7/28 Roger Binns
> If they don't allow you to turn on extension loading then only core changes
> to SQLite will (eventually) get through, or the development environment
> getting friendlier or the user deciding to use a different environment that
> isn't so
Yes, pragma table_info on a non-existent table is good example. I think we
can only return NULL and don't create the table in this case:
sqlite> .load ./libsqlitepragmacols.so
sqlite> select pragma_cols('pragma table_info(sqlite_master2)')='';
sqlite> select pragma_cols('pragma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2010 01:52 PM, Alexey Pechnikov wrote:
> Why difficulty?
I meant supporting any possible pragma, without having to hard code a list
of column names for each one. Implementing your approach and using virtual
tables both require knowing the
I'm sorry, see right link for added file pragmacols.c:
http://sqlite.mobigroup.ru/artifact?name=1ef363e38a2fef3ed64a6659079264524d6bc0e0
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
___
sqlite-users mailing list
sqlite-users@sqlite.org
2010/7/27 Roger Binns
> I had also considered doing one. The approach I would have taken is using
> virtual tables where you could supply the pragma statement as the first
> parameter to the table. The difficulty is in knowing what column names
> should be returned as I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2010 11:36 AM, Alexey Pechnikov wrote:
> I did write pragmawrapper extension
I had also considered doing one. The approach I would have taken is using
virtual tables where you could supply the pragma statement as the first
parameter to the
I did write pragmawrapper extension because there are a lot of traffic in
this topic. It's terrible to read these messages ;-)
See http://sqlite.mobigroup.ru/dir?name=ext/_pragmawrapper
Compile as
gcc -shared pragmawrapper.c -o libsqlitepragmawrapper.so
Use as
.load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2010 07:07 AM, Tim Romano wrote:
> I will consider it progress if we could get beyond the two stock replies:
> "you should do that in your application" and "you could do that in an
> extension".
You seem to think I am sort of gatekeeper of
Roger,
I do not expect my request to be a priority. I have suggested only that
such black-box amalgamations be kept in mind as a mitigating factor when the
architects are assigning a priority to a feature request. In those cases
where it is impossible for the end-user to avail himself of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2010 12:17 PM, Tim Romano wrote:
> But Roger, the "layer sitting in front of SQLite" is a programming
> environment which provides its own (black-box) connectivity to SQLite, and
> it isn't going to be calling any DLL into which one will
>But Roger, the "layer sitting in front of SQLite" is a programming
>environment which provides its own (black-box) connectivity to SQLite, and
>it isn't going to be calling any DLL into which one will have injected
>a UDF
>library in the manner you have laid out, and it's not going to let the
But Roger, the "layer sitting in front of SQLite" is a programming
environment which provides its own (black-box) connectivity to SQLite, and
it isn't going to be calling any DLL into which one will have injected a UDF
library in the manner you have laid out, and it's not going to let the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2010 06:03 AM, Tim Romano wrote:
> The goal is to expose the UDF to the "layer sitting in front". Are you
> saying sqlite3_auto_extension allows me to run a program, once, that will
> register a piece of code that is loaded whenever ANY
Since this discussion might help the OP too, I hope it's not regarded as a
thread hijack. I will create a new thread otherwise. Mr. v3meo, your
thoughts?
A question about this advice:
"If the layer sitting in front of SQLite doesn't
expose create function then you can still do so. Load the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/25/2010 07:08 AM, Tim Romano wrote:
> Something that can be knocked out in a half-hour
Nothing gets banged out in half an hour with SQLite :-) Using a string
reverse example:
- - The code has to be hooked in various places
- - The function
Roger,
Clearly not every feature that has found its way into SQLite is useful
to "the majority" of the user base, but I will accept the core philosophical
position here as not unreasonable--a requested feature that benefits very
few use-cases might well be placed lower on the to-do list than one
"Roger Binns" wrote in
message news:4c4b1ca7.1040...@rogerbinns.com...
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/24/2010 05:38 AM, ve3meo wrote:
>> I am a humble user of the command line implementation and of various
>> SQLite
>> managers and not an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2010 05:38 AM, ve3meo wrote:
> I am a humble user of the command line implementation and of various SQLite
> managers and not an application developer so I cannot do it in code.
You are coding! The command line tool is merely a thin
On Sat, 24 Jul 2010 08:38:31 -0400, "ve3meo"
wrote:
>"Roger Binns" wrote in
>message news:4c4a5bd5.5010...@rogerbinns.com...
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 07/23/2010 07:47 PM, ve3meo wrote:
>>> Is it possible to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/24/2010 04:42 AM, Tim Romano wrote:
> Quite a few users of SQLite these days are not wrapping
> the SQLite libraries in their own client app but are communicating with the
> database via a bridge as if it were a remote server engine.
Yes, but
"Roger Binns" wrote in
message news:4c4a5bd5.5010...@rogerbinns.com...
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/23/2010 07:47 PM, ve3meo wrote:
>> Is it possible to store the results of a PRAGMA statement, especially
>> PRAGMA
>> database_list in a
Tim,
I, like you, am using SQLite as the DB to a web server. But I have to agree
with Roger. I do so from the prospective that web client cannot make native
calls to SQLite. Thus the web server is the client. Further more I would
say that in all web server based solutions, the web server is
Roger,
It would be more accurate to say that SQL is a library which *can* live
inside an application. Whether it actually does live inside it will depend
on how one is using SQLite. When it is used as a "back-end" reached via
middleware, such as the ADO.NET driver, SQLite does not live inside
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2010 07:47 PM, ve3meo wrote:
> Is it possible to store the results of a PRAGMA statement, especially PRAGMA
> database_list in a SQLite temporary table using only SQLite commands?
No. Is there any particular reason your code can't copy
27 matches
Mail list logo