[sqlite] POSIX and MMU (was Re: out of the void: xDlSym)

2016-01-17 Thread Howard Chu
Scott Robison wrote: > On Sat, Jan 16, 2016 at 1:58 PM, James K. Lowden > wrote: > >> On Fri, 15 Jan 2016 21:41:41 -0500 >> Richard Damon wrote: >> >>> there are machines where it doesn't work (you just need a larger >>> program space than data space). >> >> Huh. An example of which is the "medi

[sqlite] POSIX and MMU (was Re: out of the void: xDlSym)

2016-01-17 Thread Scott Robison
On Sun, Jan 17, 2016 at 1:33 PM, Howard Chu wrote: > Scott Robison wrote: > >> Sorry for the OT diversion, but I'm just curious as I don't have >> historical >> POSIX standards for reference. Does POSIX really *require* an MMU? >> Certainly Unix like systems were written for 8086 class computers,

[sqlite] POSIX and MMU (was Re: out of the void: xDlSym)

2016-01-17 Thread Scott Robison
On Sun, Jan 17, 2016 at 10:09 AM, James K. Lowden wrote: > On Sat, 16 Jan 2016 14:21:26 -0700 > Scott Robison wrote: > > > > Huh. An example of which is the "medium model" of the Intel 8086: > > > 20-bit code pointers and 16-bit data pointers. A machine for which > > > C compilers existed, and

[sqlite] POSIX and MMU (was Re: out of the void: xDlSym)

2016-01-17 Thread James K. Lowden
On Sat, 16 Jan 2016 14:21:26 -0700 Scott Robison wrote: > > Huh. An example of which is the "medium model" of the Intel 8086: > > 20-bit code pointers and 16-bit data pointers. A machine for which > > C compilers existed, and on which no Posix system will ever run > > (because it lacks an MMU).

[sqlite] Updating the contents of a field in table A with the value of the same field in table B

2016-01-17 Thread James K. Lowden
On Sat, 16 Jan 2016 14:26:20 -0700 "Keith Medcalf" wrote: > > the result is nondeterministic if more than one row in S matches. > > The update applies all rows in S matching T. Of course, only the > > last one is preserved. Of course, because order is nonsemantic, > > there's no way to know *wh

[sqlite] SQLite3 with support for _Decimal64 on github

2016-01-17 Thread Domingo Alvarez Duarte
Hello ! I finally got time to publish my changes to sqlite3 to allow the use of _Decimal64/double/int64 as floating point unit by defining SQLITE_USE_DECIMAL, almost all tests pass with exception of direct binary manipulation of doubles (_Decimal64 have different binary representation) and "with

[sqlite] Parsing the contents of a field

2016-01-17 Thread R Smith
On 2016/01/16 4:53 PM, Simon Slavin wrote: > On 16 Jan 2016, at 2:31pm, R Smith wrote: > >> There is of course no SQL function to do this, but thanks to CTE we can >> achieve it easily (though not extremely efficiently). > I thought that WITH could be used only for SELECT statements. > > Oh wai

[sqlite] Parsing the contents of a field

2016-01-17 Thread Simon Slavin
On 17 Jan 2016, at 12:27am, R Smith wrote: > I quote from the documentation at: https://www.sqlite.org/lang_with.html > > "All common table expressions (ordinary and recursive) are created by > prepending a WITH clause in front of a SELECT, INSERT, DELETE, or UPDATE > statement. A single WITH