Re: [sqlite] sqlite syntax auto suggest

2019-11-28 Thread Richard Hipp
On 11/28/19, Laurent Dhont wrote: > is there an API to > get this information in a format that is not an image? By coincidence, I checked in a change two days ago that might be helpful. See https://www.sqlite.org/src/timeline?c=4dbd398d640852d4 for the specific check-in. If you now build SQLite

[sqlite] sqlite syntax auto suggest

2019-11-28 Thread Laurent Dhont
Hi all, I am trying to create a fully automated auto suggestion feature for my web application for sqlite. Currently this is going well, but I realized there are to many features in sqlite to hardcode this, so it will be near impossible and take a lot off time. The diagrams on the site of sql

Re: [sqlite] built-in printf() not supporting \n or \t ?

2019-11-28 Thread Keith Medcalf
On Thursday, 28 November, 2019 09:21, Richard Damon wrote: >\n and \t are not 'printf' features, but C string features, that \ is an >escape introducer for compiling a string, and if followed by a letter >like n or t it builds a string with the special value represented by >that function. The \

Re: [sqlite] built-in printf() not supporting \n or \t ?

2019-11-28 Thread Richard Damon
On 11/28/19 10:24 AM, Dominique Devienne wrote: > Obviously it's ugly to use concatenation and char() to format a string > literal with tabs and newlines. > Is there a better way? Why doesn't printf() support newlines and tabs like > it's C cousin? --DD > > PS: Built-in printf() also doesn't suppor

[sqlite] built-in printf() not supporting \n or \t ?

2019-11-28 Thread Dominique Devienne
Obviously it's ugly to use concatenation and char() to format a string literal with tabs and newlines. Is there a better way? Why doesn't printf() support newlines and tabs like it's C cousin? --DD PS: Built-in printf() also doesn't support positional params, to "emulate" newline with printf( '%1$

Re: [sqlite] [EXTERNAL] virtual tables vs. expression-based indexes

2019-11-28 Thread Hick Gunter
If your external data store can maintain an index on some expression, then exposing that index as a computed field is the way to go with a virtual table. Alternatively, you can expose the index as a separate virtual table with a "foreign key" that references the original virtual table and join t