On 09/26/2018 01:14 PM, Deon Brewis wrote:
I am receiving an integrity check failure on 3.26 on the 9/19/2018 drop. It's
not everywhere and it may be coincidental, but it may also be related to the
new change where expression indexes aren't updated if their columns aren't
modified.
I'm gettin
I am receiving an integrity check failure on 3.26 on the 9/19/2018 drop. It's
not everywhere and it may be coincidental, but it may also be related to the
new change where expression indexes aren't updated if their columns aren't
modified.
I'm getting these integrity check failures:
wrong # of
No, I have not. The .timer discrepancy is due to the overhead of memory
management which is done via DPC's and thus they accrue to the Supervisor and
not the user process, the user process sees it as missing time. The underlying
issue with the cache stride management has not been addressed ye
Actually no, the calculation is based on the Julian Day number in the struct
DateTime.
When you "load" a struct DateTime from a "string", the string is parsed and the
constituent parts are used to create the JulianDay (iJD) field of the
structure. This means that the iJD value is then relat
On Tue Sep 25, 2018 at 09:48:27AM -0400, Richard Hipp wrote:
> On 9/25/18, Nathan Wagner wrote:
> > I am working up code to calculate a hash over parts of the data in an sqlite
> > database, and as a start looked at the dbhash.c code found at
>
> Consider instead using one of these:
>
> http
You're kind of asking if a 4 cylinder engine can outrun an 8 cylinder
engine by just physically looking at the engines. The answer is yes. It
can. Given the right circumstances.
Your transfer rates are going to be subjective based on your hardware, network
speeds at the source and destination (
I think that you can infer it from the statement that "The GLOB operator
is similar to LIKE". The documentation for the "LIKE" operator notes
explicitly that the right-hand operand is the pattern (needle) and the
left-hand operand is the string to match against the pattern (haystack).
That said, i
Hello,
I have created a database to database transfer plugin for
my application. The plugin is functional and I have
collected a log of testing results stored in a SQLite db.
The links below are of the database and definition of
parameters fields. The main exception, dbTypeMemory,
meaning memory o
I'm looking at https://sqlite.org/lang_corefunc.html#glob - and glob()
seemed like it might help me with a problem.
But the docs don't actually say what X and Y are. Which is the needle
and which is the haystack? It does say "The glob(X,Y) function is
equivalent to the expression "Y GLOB X"."
Hi David,
Thanks for the recovery tip. Fortunately this was simple to recover from
by re-attaching as the "approved" name and then dropping the offending
view using a standard "DROP VIEW a_view;" query.
On 2018-09-25 17:25, David Raymond wrote:
I think I'd be inclined to have it give the er
I think I'd be inclined to have it give the error first rather than rename it.
But that's just me.
If you need to recover, you can do it with pragma writable_schema to delete the
line from sqlite_master.
D:\Temp>sqlite3
SQLite version 3.25.1 2018-09-18 20:20:44
Enter ".help" for usage hints.
Hi List,
I just caught myself in a little circle and accidentally created a
semi-invalid database. I was wondering if it's something SQLite's query
parser could self-resolve / alert about.
Attach a database as "my_attachment" schema name, and then run:
CREATE VIEW my_attachment.a_view AS
On 2018-09-19 2:30 p.m., Brad Spencer wrote:
In sqlite-3.25.0, the release notes say the following:
"Fix table rename feature so that it also updates references to the
renamed table in triggers and views."
...
However, because of this change, the "completely general" procedure on
the ALTER TA
Hello !
Yes you are right the compression need to be defined by each field that
you want to be compressed, I did it because I need some fields that the
general size do not justify the overhead of the compression.
Cheers !
On 25/09/2018 14:29, Wout Mertens wrote:
This is really cool, thanks
On 9/25/18, Nathan Wagner wrote:
> I am working up code to calculate a hash over parts of the data in an sqlite
> database, and as a start looked at the dbhash.c code found at
Consider instead using one of these:
https://www.sqlite.org/src/file/ext/misc/sha1.c
https://www.sqlite.org/src/
I am working up code to calculate a hash over parts of the data in an sqlite
database, and as a start looked at the dbhash.c code found at
https://www.sqlite.org/src/artifact?ci=trunk&filename=tool/dbhash.c
I don't think the code as is works correctly, it is easy to construct
a hash collision bet
This is really cool, thanks for sharing!
I wonder though, is the compression done per field? I read the source but I
couldn't figure it out quickly (not really used to the sqlite codebase).
What are the compression ratios you achieve?
Wout.
On Mon, Sep 24, 2018 at 3:58 PM Domingo Alvarez Duart
17 matches
Mail list logo