I just want to point something out that might help the original poster.
On Saturday, March 7, 2020, 7:00:21 AM EST,
sqlite-users-requ...@mailinglists.sqlite.org
wrote: >
> 1. NULL is NULL = Yes, True,
> 2. NULL is FALSE = Nope, False.
> 3. NULL is TRUE = Nope, False.
> 4. NULL is
All these subject lines about UDTs in SQLite and the one and only thing I would
use such a thing for is not listed: Date/Time values. I'd love for there to be
native date/time formats in SQLite. I'm surprised it never came up. Although
I'm also surprised the NoSQL-ite came up.
> That's six
I'm surprised no one suggested a virtual table interface to the OP's blob.
Store the blob of complex numbers as a blob in raw form (he said it was a
single platform so endian concerns don't matter) and then create a virtual
table that provides the array index into the complex numbers. Add a few
Words aren't big enough on that page. I was expecting to find a link where
things are posted. It was a case of TL;DR.
>
> From: Roger Binns <rog...@rogerbinns.com>
>To: Joe Mucchiello <jmucchie...@yahoo.com>; General Discussion of SQLite
&g
Sorry, but if VS13 is a supported compiler. Then whatever it reports as an
error should be fixed. Not everyone who grabs the amalgam file to compile it
can figure out how to "fix" compiler errors. Are you saying it is not worth
suppressing this error just because it's only in one compiler?
So I'm posting it here. The 3.8.6 Amalgam file generates an error in VS13 on
Windows:
sqlite3.c(77874): error C4703: potentially uninitialized local pointer variable
'pReadr' used
This is from the source file src/vbesort.c in a function called
vdbeSorterSetupMerge:
PmaReader *pReadr;
So I'm posting it here. The 3.8.6 Amalgam file generates an error in VS13 on
Windows:
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
7 matches
Mail list logo
