Same code, same compile options, same compiler version
options -s -O3 -pipe -march=native -mtune=native -falign-functions=16
-falign-loops=16 -flto
32-bit GCC 4.9.3
>speedtest1 --size 1000
-- Speedtest1 for SQLite 3.15.0 2016-08-17 11:14:39
a861713cc6a3868a1c89240e8340bc
100 - 50
Richard,
On Thu, Aug 18, 2016 at 2:23 AM, Rousselot, Richard A
wrote:
I was only interested in doing these calculations quickly; that is my
real-world. The SQL scripts I am using were built with multiple
steps with intermediate temp tables that are used
Sorry got confused with Sqlite sites, created this ticket at
system.data.sqlite.org yesterday.
Regards,
Winter
Ticket UUID: 4ca56c780c92f6e308abf1ad5bb76be2a3e29a68
Title: AsyncTableQuery "Where" clause can't handle "OR" (||).
Status: Open Type: Code_Defect
Severity: Important Priority:
Effectively,
Sorry about my mistake.
2016-08-17 10:33 GMT+02:00 Richard Hipp :
> On 8/17/16, flo wrote:
> >
> > $ sqlite3 test.db "UPDATE test SET id=0 AND name='new_name' AND age=30
> > WHERE id=1;"
>
> The above is parsed like this:
>
> UPDATE test
Simon,
I was only interested in doing these calculations quickly; that is my
real-world. The SQL scripts I am using were built with multiple steps with
intermediate temp tables that are used to create a final result table.
I understand my needs are not generally how others use SQLite. I am
On 17 Aug 2016, at 4:54pm, Rousselot, Richard A
wrote:
>PRAGMA journal_mode = Off;
This configuration is designed for cases where the resulting database will be
thrown away soon (e.g. when the application quits). It does increase speed
greatly,
On 8/17/16, sanhua.zh wrote:
> sqlite3_test_control() is an interface for testing. Is it safe to use it in
> released product?
It is "safe" if you statically link against a version of SQLite that
supports the behavior you want. It is not safe if you try to use
whatever
Speed improvements based on 64-bit MinGW.
SQLite 3.14.2, built with MinGW 64-bit. -
https://sourceforge.net/projects/mingw-w64/?source=typ_redirect
gcc -m64 -O2 -DSQLITE_THREADSAFE=0 shell.c sqlite3.c -o sqlite3.exe
gcc -g -shared extension-functions.c -o extension-function.dll
Built with SQLITE
Hi Richard,
Thanks for your answer. I had been looking at the csv exported data in Excel
and it looked right.
I opened the csv file in a plain text editor and it was as you said, the data
was already in date format. Formatting the Column and re-exporting the csv
file corrected my issue.
sanhua.zh wrote:
> sqlite3_test_control() is an interface for testing. Is it safe to use it in
> released product?
This question does not make sense. You need to modify your copy of the
SQLite library to actually do something with the reserved bytes, so you
have complete control over setting
Ward WIllats wrote:
> sqlite> attach database '/tmp/RareData.db' as rd; < ATTACH SECOND DB
> sqlite> pragma page_size=512; <- SET MAIN DB PAGE SIZE
> ...
> sqlite> pragma journal_mode=WAL;
This sets the journal mode of _both_ databases to WAL.
This requires that both database
On 2016/08/17 11:04 AM, Simon Davies wrote:
On 17 August 2016 at 09:39, R Smith wrote:
On 2016/08/17 9:05 AM, flo wrote:
Hi everyone,
.
.
.
Well, it is perfectly valid to give boolean operations as an expression.
If I said " id = 3 AND 6 then the resulting value would
On 17 August 2016 at 09:39, R Smith wrote:
>
>
> On 2016/08/17 9:05 AM, flo wrote:
>>
>> Hi everyone,
.
.
.
> Well, it is perfectly valid to give boolean operations as an expression.
> If I said " id = 3 AND 6 then the resulting value would be 2 (If you are
> unsure why that
On 2016/08/17 4:54 AM, Aaron Paul wrote:
Greetings,
I’m importing a csv file into a newly created table with .import. One of the
columns contain a numerical tag which sometimes resembles a date (example
08-17).
These are not dates, but the .import is converting 08-17 into 17-Aug
The odd
On 2016/08/17 9:05 AM, flo wrote:
Hi everyone,
I found a reproducible bug on the SQL UPDATE statement parsing. Here is the
details.
I 've try to update some data on a SQLite database with a outlandish syntax
with "AND" between the columns to be update. The SQL didn't fail but the
data
Your UPDATE statement does not mean what you think it means.
UPDATE test SET id=0 AND name='new_name' AND age=30 WHERE id=1;
Is parsed as:
UPDATE test SET id = (0 AND name='new_name' AND age=30) WHERE id=1;
The expression (0 AND ...) will always evaluate to 0.
-Ursprüngliche
On 8/17/16, flo wrote:
>
> $ sqlite3 test.db "UPDATE test SET id=0 AND name='new_name' AND age=30
> WHERE id=1;"
The above is parsed like this:
UPDATE test SET id = (0 AND name='new_name' AND age=30) WHERE id=1;
And since the expression in parentheses always evaluates
On 8/16/16, Aaron Paul wrote:
> Greetings,
>
> I’m importing a csv file into a newly created table with .import. One of
> the columns contain a numerical tag which sometimes resembles a date
> (example 08-17).
>
> These are not dates, but the .import is converting
Greetings,
I’m importing a csv file into a newly created table with .import. One of the
columns contain a numerical tag which sometimes resembles a date (example
08-17).
These are not dates, but the .import is converting 08-17 into 17-Aug
The odd thing is it is doing this even when the
Hi everyone,
I found a reproducible bug on the SQL UPDATE statement parsing. Here is the
details.
I 've try to update some data on a SQLite database with a outlandish syntax
with "AND" between the columns to be update. The SQL didn't fail but the
data update was incomplete.
The SQLite version
20 matches
Mail list logo