Yes, that old version (from about 2 years ago) crashes (on Windows).
No, the current one does not crash and produces two output lines.
This is using your test SQL with the spelling errors fixed.
CREATE TABLE mimmo (key TEXT PRIMARY KEY, value TEXT, valueJson TEXT, blockNo
INTEGER, txnNo
Partial traceback (bdb 18.1.32):
Program received signal SIGSEGV, Segmentation fault.
0x7798e560 in jsonEachColumn () from ./lib/libdb_sql-18.1.so
(gdb) bt full
#0 0x7798e560 in jsonEachColumn () from ./lib/libdb_sql-18.1.so
No symbol table info available.
#1 0x779b29b6
While looking through the SQLite3 source trying to find answers to some
questions I had about virtual tables, I noticed that the memory DB is
implemented as a VFS rather than a database. Is my understanding correct
that this means that the estimated cost the query planner uses for memory
tables
Note https://www.sqlite.org/datatype3.html says:
"Applications can chose to store dates and times in any of these
formats and freely convert between formats using the built-in date and
time functions."
This is partially true. The date and time functions will optionally
parse 'a timezone indicator
I'm using sqlite with BDB as the persistence store; if you can't
reproduce it (same sqlite version), I suppose it means it's a BerkeleyDB
issue, and I'll follow up with them.
Thanks!
On 7/23/2019 12:01, Richard Hipp wrote:
Unable to reproduce. Are you sure you are sending the correct script?
Unable to reproduce. Are you sure you are sending the correct script?
What operating system are you running on? How did you compile
SQLite?
On 7/23/19, Carlo Innocenti wrote:
> I have a segmentation fault which happens when trying to run a subquery
> based on json_each() if the argument is
I have a segmentation fault which happens when trying to run a subquery
based on json_each() if the argument is the value of an outer
json_each() row:
CREATE TABLE mimmo (key TEXT PRIMARY KEY, value TEXT, valueJson
TEXT, blockNo INTEGER, txnNo INTEGER, metadata TEXT);
INSER INTO mimmo
On Tue Jul 23, 2019 at 04:41:59PM +0200, Andreas Kretzer wrote:
> Am 23.07.2019 um 16:22 schrieb Steve Leonard:
> >
> > 4)I have tried several combinations of creating a new field
> > of type numeric, blob, real, and integer and then tried to update
If you want to work with date *strings* of the
Hi Steve,
beside what I said in my last statement, you should also
have a look at
https://www.sqlite.org/datatype3.html
https://www.sqlite.org/lang_datefunc.html
This may help you to understand, how SQLite handles specific
data types, that might be understood (or at least be handled)
Am 23.07.2019 um 16:22 schrieb Steve Leonard:
>
> 1) I imported a new table using dbbrowser for sqlite from a csv file
> one of the fields is named myfdat and the first record contains
> '12/01/2011'
>
> 2) the import created a table with the field myfdt as type text and
> the value matches the
1) I imported a new table using dbbrowser for sqlite from a csv file
one of the fields is named myfdat and the first record contains '12/01/2011'
2) the import created a table with the field myfdt as type text and the
value matches the csv file
3) I want to select all records where myfdt is
Hi Guys
I want to write an application in kotlin which uses SQLITE.
Is there already a good Kotlin package which provides SQLITE services (I know
that there is one for Android development, but I’m not
developing on top of Android)
Thanks
___
12 matches
Mail list logo
