Re: [sqlite] feature req: PLEASE why the heck COMMENT fields are not supporte in years!!

Patches are still welcome, I guess. I haven't seen anybody claiming that this would be done in any way. On 6 June 2017 at 15:17, PICCORO McKAY Lenz wrote: > how its the status of this work? > > a limited implementation will be good! > > Lenz McKAY Gerardo (PICCORO) >

Re: [sqlite] RIGHT JOIN! still not supported?

Seeing how SQLite was created in 2000, it seems like nobody really needed this feature for the last 17 years enough in order to actually implement it. Last I heard, patches are welcome on this mailing list. Don't keep us waiting. Kind regards, Daniel On 20 March 2017 at 21:09, PICCORO McKAY

Re: [sqlite] tclsqlite3 db function exports not visible on other connections. Why not?

You can use sqlite3_auto_extension for this. On 19 March 2017 at 11:35, R Smith wrote: > > On 2017/03/19 11:05 AM, petern wrote: >> >> Taking DRH's remarks about learning tclsqlite for the efficient coding to >> heart, I discovered a big problem. >> >> Here is the simplest

Re: [sqlite] IS NULL and IS NOT NULL constraints not passed into virtual table's xBestIndex

Thanks a ton for the replies. This pretty much confirms what I've been suspecting. On 3 February 2017 at 11:24, Clemens Ladisch wrote: > The FTS and R-tree virtual tables do not contain NULL values, so > I guess it was never seen as necessary. Does this make it an accidental

[sqlite] IS NULL and IS NOT NULL constraints not passed into virtual table's xBestIndex

Hi. I'd like to ask why using a IS NULL or IS NOT NULL constraint in a query made to a virtual table does not result in these constraints being present in the sqlite3_index_info structure passed to the virtual table's xBestIndex. Currently, using one of these constraints results in no constraints