Re: [sqlite] SQLITE_MAX_COLUMN should be a runtime knob for Machine Learning

Le lun. 17 juin 2019 à 14:36, Simon Slavin a écrit : > On 17 Jun 2019, at 9:14am, Dominique Devienne wrote: > > > SQLite4's LSM backend is now an extension in SQLite3 called LSM1 > > https://www.sqlite.org/cgi/src/dir?ci=trunk&name=ext/lsm1&type=tree > > > > Which has been discussed in this list

[sqlite] nested set tree: how to change order of one node?

The tree in question contains categories, subcategories and finally image galleries. It is common for the user to want to sort all the subordinates of one level a different way, at times alphanumeric, other times simply to their liking. I have been reading through Joe Celko's Trees and Hierarchie

[sqlite] CVE-2019-5018 patch

Hi, What is exactly the patch for CVE-2019-5018? I could not see it anywhere in the release changelog nor in the Cisco Talos report. It would be useful for distributions that need to backport the fix. Thanks, -- Riccardo Schirone Red Hat -- Product Security Email: rschi...@redhat.com PGP-Key ID:

Re: [sqlite] CVE-2019-5018 patch

On 18/6/62 19:48, Riccardo Schirone wrote: Hi, What is exactly the patch for CVE-2019-5018? I could not see it anywhere in the release changelog nor in the Cisco Talos report. It would be useful for distributions that need to backport the fix. It was this one: https://sqlite.org/src/info/1e1

Re: [sqlite] Please explain multi-access behaviour to me

This has been a very informative and helpful discussion. Thank you. So have I understood correctly, that in an application, this kind of SQLITE_BUSY handling is sufficient: BEGIN UPDATE #1 SELECT #2 UPDATE #3 COMMIT <- check for busy here and retry only the commit on failure And second, wha

Re: [sqlite] nested set tree: how to change order of one node?

Sam, Can't answer your question directly, maybe the closure extension is something for you. To read a bit about it: http://charlesleifer.com/blog/querying-tree-structures-in-sqlite-using-python-and-the-transitive-closure-extension/ ingo On 18-6-2019 14:19, Sam Carleton wrote: > My thought proces

Re: [sqlite] CVE-2019-5018 patch

On 06/18, Dan Kennedy wrote: > > On 18/6/62 19:48, Riccardo Schirone wrote: > > Hi, > > > > What is exactly the patch for CVE-2019-5018? I could not see it anywhere in > > the release changelog nor in the Cisco Talos report. It would be useful for > > distributions that need to backport the fix.

Re: [sqlite] Please explain multi-access behaviour to me

On Tuesday, 18 June, 2019 07:12, Thomas Kurz wrote: >This has been a very informative and helpful discussion. Thank you. >So have I understood correctly, that in an application, this kind of >SQLITE_BUSY handling is sufficient: >BEGIN >UPDATE #1 >SELECT #2 >UPDATE #3 >COMMIT <- check for b

Re: [sqlite] Please explain multi-access behaviour to me

"UPDATE #1 completes" and "SELECT #1 completes" should be read as the first sqlite3_step of that statement returns some sort of success indicator ... Note that the sequence: BEGIN; SELECT #1; UPDATE #1 may result in a deadlock in that although SELECT #1 may be able to obtain a SHARED lock, UP

Re: [sqlite] Please explain multi-access behaviour to me

On 18 Jun 2019, at 2:11pm, Thomas Kurz wrote: > So have I understood correctly, that in an application, this kind of > SQLITE_BUSY handling is sufficient: > > BEGIN > UPDATE #1 > SELECT #2 > UPDATE #3 > COMMIT <- check for busy here and retry only the commit on failure I believe that the a

Re: [sqlite] Understanding the WITH clause

On Mon, 17 Jun 2019 20:46:41 -0400 Sam Carleton wrote: > It is my view that peace is not something that can be defined with > some words, rather it is a universal experience. "But peace is not merely the absence of this tension, but the presence of justice." -- MLK, Letter from

Re: [sqlite] Please explain multi-access behaviour to me

Hi, Actually, you're better off setting a timeout rather than handling retry in your own code: As I understand it, SQLITE_BUSY can occur in two situations: one where busy looping will fix it and one where it won't. Using the busy_timeout handles

Re: [sqlite] Please explain multi-access behaviour to me

Andy Bennett, on Tuesday, June 18, 2019 03:53 PM, wrote... > > > Actually, you're better off setting a timeout rather than handling > > retry in your own code: > > > > > > As I understand it, SQLITE_BUSY can occur in two situations: one where > busy loo

[sqlite] Is this a bug?

Dear SQLiters, I can not figure out what I am doing wrong. In testing, I simplified to the following: CREATE TABLE cosSquared(refVolume INT, vecVolume INT, cosSquared REAL); SELECT refVolume, CAST(10*max(cosSquared) AS INT) FROM cosSquared GROUP BY refVolume; refVolume CAST(10*max(cosSquar

Re: [sqlite] Is this a bug?

Your nested select statement wants to return many rows. Technically I think this is illegal SQL (?), but it looks like SQLite is being lax about this as usual and doing what it normally does in this sort of situation: picks a row at random from the inner select. Your statement is more or less equi

Re: [sqlite] Is this a bug?

Oh, Thank you Barry. I am glad it is not a bug. Bug is in my head. Thank you, Roman From: sqlite-users [sqlite-users-boun...@mailinglists.sqlite.org] on behalf of Barry [smith.bar...@gmail.com] Sent: Tuesday, June 18, 2019 7:59 PM To: SQLite mailing li