Re: [sqlite] Suggestion to add "locate" as a broader version of "instr"

On 10 Mar 2014, at 1:38am, Stephen Chrzanowski wrote: > Apologies for the interruption and sort of off topic, but, is .timer part > of the CLI only or is it part of the SQL language? Can I get the result of > a timer from a call, or do I have to put a wrapper on my

Re: [sqlite] Suggestion to add "locate" as a broader version of "instr"

On Sunday, 9 March, 2014 19:38, Stephen Chrzanowski inquired: >Apologies for the interruption and sort of off topic, but, is .timer part >of the CLI only or is it part of the SQL language? Can I get the result >of a timer from a call, or do I have to put a wrapper on my

Re: [sqlite] Suggestion to add "locate" as a broader version of "instr"

Apologies for the interruption and sort of off topic, but, is .timer part of the CLI only or is it part of the SQL language? Can I get the result of a timer from a call, or do I have to put a wrapper on my wrapper? On Sun, Mar 9, 2014 at 8:17 PM, Keith Medcalf wrote: > >

Re: [sqlite] Suggestion to add "locate" as a broader version of "instr"

sqlite> create virtual table n using wholenumber; sqlite> .timer on sqlite> select sum(sqrt(value)) from n where value between 1 and 1000; 21097.4558874807 Run Time: real 0.001 user 0.00 sys 0.00 sqlite> select sum(sqrt(value)) from n where value between 1 and 100; 67166.458841

Re: [sqlite] Making string changes in a table

On 3/9/2014 6:37 PM, Tim Streater wrote: Dammit, I looked up and down for 'strlen' and passed over 'length'! I had been thinking about: update mytable set path='/path/from/' || substr(path, length('/path/to/') + 1) where path like '/path/to/%'; that way I anchor to the start of the

Re: [sqlite] Making string changes in a table

On 09 Mar 2014 at 22:17, Igor Tandetnik wrote: > On 3/9/2014 6:05 PM, Tim Streater wrote: >> I have a table with one column containing file paths, such as /path/to/file >> and /path/to/my/otherfile. Now I want to change all entries where the path >> starts as /path/to/ to

Re: [sqlite] Making string changes in a table

On 3/9/2014 6:05 PM, Tim Streater wrote: I have a table with one column containing file paths, such as /path/to/file and /path/to/my/otherfile. Now I want to change all entries where the path starts as /path/to/ to /path/from/. Getting a candidate list is easy, and I can then make the changes

Re: [sqlite] Making string changes in a table

On 3/9/14, Simon Slavin wrote: > Check out REPLACE(): > > Technically speaking this might mess up if the string '/path/to/' occurs in > the middle of the string as well as at its beginning, For that reason, I think it would be better to use the substr function. Ambrus

Re: [sqlite] Making string changes in a table

On 9 Mar 2014, at 10:05pm, Tim Streater wrote: > I have a table with one column containing file paths, such as /path/to/file > and /path/to/my/otherfile. Now I want to change all entries where the path > starts as /path/to/ to /path/from/. Getting a candidate list is

[sqlite] Making string changes in a table

I have a table with one column containing file paths, such as /path/to/file and /path/to/my/otherfile. Now I want to change all entries where the path starts as /path/to/ to /path/from/. Getting a candidate list is easy, and I can then make the changes in PHP and rewrite the rows, but I

Re: [sqlite] Out of memory error for SELECT char();

Eduardo Morras wrote: > On Sat, 8 Mar 2014 14:09:17 -0500 > Richard Hipp wrote: >> It isn't really running out of memory >> >> The implementation of char() allocates 4 bytes of output buffer for >> each input character, which is sufficient to hold any valid unicode >>

Re: [sqlite] Out of memory error for SELECT char();

On Sat, 8 Mar 2014 14:09:17 -0500 Richard Hipp wrote: > It isn't really running out of memory > > The implementation of char() allocates 4 bytes of output buffer for > each input character, which is sufficient to hold any valid unicode > codepoint. But with zero input

Re: [sqlite] Suggestion to add "locate" as a broader version of "instr"

Hello Max, Your link is pretty interesting. It looks that : - method1 should be easily implemented with SQLite "floating point" representation, - and with a very very small code size. Here is the benchmarking of the two available methods :