#example-vtable
I believe the wrappers for other languages are similar. Of course for
a book you'd have to pick a language/wrapper and hope it is acceptable
for the audience.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlTdBHMACgkQmOOfHg372QRvYgCgg0Y1/Scvo+SGwOvPLkq3zBCF
with what it is you are trying to do.
Disclosure: I'm the author of an alternate Python SQLite wrapper:
http://rogerbinns.github.io/apsw/
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlTc3AQACgkQmOOfHg372QSejACg5etNEUcBnNq0rKQV2cABkPo6
bjwAn0FagmG7B8jUxTCSEWDzLbMhOXwo
can do all this by defining SQLITE_HAS_CODEC and then providing
various functions, but you'll want to compile SQLite and the
encryption code at the same time.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlTZHdEACgkQmOOfHg372QSmWACgibDcuPzVsyfFiFcdPZSNMN6B
exposition and diagrams. SQLite is also mentioned.
http://www.slideshare.net/MarkusWinand/modern-sql
Seen on HackerNews:
https://news.ycombinator.com/item?id=9018129
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlTYB58ACgkQmOOfHg372QSipwCfTJa/M8UPBqQ1UwRmoxgTVSwU
information first and if
there signals a Python exception. Only if that is None does it check
the sqlite api return code, so that error (SQLITE_ABORT in this case)
will not be signalled.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
approaches that work better.
How often do you want the size (eg a one off, checked every few minutes)?
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlTSsNoACgkQmOOfHg372QS+VgCguwbCzace81zpwYNueblRu0Qj
85AAnR0XRX4Mw8DBlgu2Tfq04+/ng5Nc
=7HiF
-END PGP SIGNATURE
this out. We don't have access to your systems, or a way to
reproduce, and SQLite doesn't have code to cause this.
A tool that may help is SystemTap.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlS+qcsACgkQmOOfHg372QTRWwCg2J2ppZfkikYm9lDIrQYTgFw5
plgAoOR2o3WSo0TFP
handle is too
complicated, so they sync everything.
You need to watch out for other write activity on the system, not just
SQLite.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlS9ZfwACgkQmOOfHg372QTsbACgzB3nBOgN3PnHo0C15IPIAQzq
2gYAoLXA3UF6bA5kNSfI31AauNQUlwu5
=uWTV
-END
stdin/out to binary mode:
http://msdn.microsoft.com/en-us/library/tw4k6df8.aspx
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlS68dsACgkQmOOfHg372QSWRQCfeBr7J/p0VhqsDwRAhDcSDq3d
MuYAoLG9R5Z3DiEHQgYTY/Ulpu7ilgIi
=/lr/
-END PGP SIGNATURE
/24/45779.aspx
http://blogs.msdn.com/b/oldnewthing/archive/2007/07/23/4003873.aspx
http://blogs.msdn.com/b/oldnewthing/archive/2015/01/07/10584656.aspx
http://blogs.msdn.com/b/oldnewthing/archive/2010/03/11/9976571.aspx
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
into binary mode:
http://support.microsoft.com/kb/58427
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlS5lz4ACgkQmOOfHg372QR6mACg4MmvKwP3pvZ0AJwLyKl08sGm
Z/0An050kV+FhIUtHnyZzKYGYEiK836s
=aG9W
-END PGP SIGNATURE
, but instead starting from the end in
reverse order.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlS4Rk8ACgkQmOOfHg372QRlLACg2Qxbn/WFJYkIUq5g/k6hiOGT
XxEAnA5UV6S6OQRBpMrqS1y2f3Gzx8IZ
=dzLI
-END PGP SIGNATURE-
___
sqlite
):
sqlite3_free( errmsg );
This way you will always free the message no matter what happened, and
will show error text if available.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSsO4QACgkQmOOfHg372QROVACeO7Kh4+bz+JME+bdRdeQbvqtt
RKoAoJlkUoluQwvITqqTDak+xCQiBtKE
=40C3
-END PGP
pysqlite's iterdump is 50 lines long. The APSW dump code (also in
Python) is 230 lines, and the SQLite shell C code is about 200 lines.
pysqlite is definitely missing many of the finer details.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
acceptable SQL.
You need to log/trace queries to find out which ones are the problems.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSrSKAACgkQmOOfHg372QRFcACaAwpOYnJwDRX3lwb3+uqSwTsT
BKsAoJ18lmnGUrNBKgPgHznYv7m0AlIW
=yR3X
-END PGP SIGNATURE
/progress_handler.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSHIZ4ACgkQmOOfHg372QResgCg1AXMQWpW0LnhKVc9k02TXRfN
P0wAoLdmiexWvkkiZOojFb7BSwZXF07X
=97eR
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users
themselves.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSFvBsACgkQmOOfHg372QRv9wCfYrybsVowHx6QTpbw/WjMoSZh
AJIAoNc4HyP1pUU/AvTGkdjJeQm93I7Y
=IKzd
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
( !@#$%^*()_+=-{}\|[]';:?/.,, etc.,
etc. in the table name);
cid|name|type|notnull|dflt_value|pk
0|||0||0
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSF764ACgkQmOOfHg372QRorQCcDbpSsjwclDLcKAiRQlFOC73M
Sc8AnirtIkzx1v/5LWrAc1VYAGJ53MnS
=bj14
-END PGP SIGNATURE
the vacuum will allow the other I/O a greater share.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSGMTgACgkQmOOfHg372QRxMACgz3qZHBGcUrOyf4DkFR5Km1a4
jm4AoL49txXLfzPQefbjlnGg9UZ4GtcP
=9gAV
-END PGP SIGNATURE-
___
sqlite
with the underlying database
changing, and how you mapped virtual table rowids to the actual
database records?
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSB+fcACgkQmOOfHg372QRZ0QCdHbaDwwE0mrE8SaITJhn5lB7K
KugAoJaBjpLVj4zemq9kqS1UsCAyvjuc
=1Jet
-END PGP SIGNATURE
comparisons simultaneously as appropriate.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSAsisACgkQmOOfHg372QQC+QCgt4YAbvrxt1luvsnhK/r2R/0Q
l4kAoI3PvnQRvmObQqqGMAGJC1cEvehf
=X77t
-END PGP SIGNATURE-
___
sqlite-users mailing list
reliably.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlSA0Y4ACgkQmOOfHg372QTCDgCfbsJR9uJ/tVlYVnnn0clU1Egr
x/YAoOUuleJXlh3XEADeAm9CO/DH47qZ
=/ItF
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/10/2014 09:41 AM, Mike McWhinney wrote:
Please let know if there are any other solutions to this database
locking problem as used on a network.
Yes. Do not do it. See the FAQ:
https://www.sqlite.org/faq.html#q5
Roger
-BEGIN PGP
://www.sqlite.org/lockingv3.html
See also:
https://www.sqlite.org/whentouse.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlRhBm8ACgkQmOOfHg372QTcLgCfblMaFauIRgE83WOcF9z2M6BV
BMYAnRSP1KwC+69vb5fUMsGeGbdImHU1
=1mbq
-END PGP SIGNATURE
));
}
// release mutex
Note this has to be done for every sqlite call that can set the error
message which is approximately all of them. Here for example is the
macro I use in my Python wrapper to do this:
https://github.com/rogerbinns/apsw/blob/master/src/util.c#L36
Roger
-BEGIN PGP
is in one file. At the top of the file I do this:
#define SQLITE_API static
#define SQLITE_EXTERN static
#include sqlite3.c
The rest of the file references the sqlite3 api as normal. None of
the symbols leak, and it is a little faster as the compiler can inline
static methods.
Roger
-BEGIN
behaviour, crashes, wrong
results etc.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlQ4dEsACgkQmOOfHg372QS17gCdGr31RcjBKe7ncvHbR8yAyoCW
dkAAoMZyiAzNIsVkirunvVWCh5ADspPq
=fCjG
-END PGP SIGNATURE-
___
sqlite-users mailing list
to look at
the various tradeoffs.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
.
For example:
pragma profile='max_performance' -- turns on all above, ups caches etc
pragma profile='min_memory'-- tunes down everything related to memory
Various members of the SQLite consortium can then do things like:
pragma profile='firefox'
Roger
as everyone assumed he couldn't spell his own name, and
corrected it to Stephanie! And his name is actually Stéphane, but don't
think any of those agencies you listed would acknowledge that.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http
of files they could get caught up in the fsync.
The spec for fsync is that it doesn't return until the file/directory is on
storage.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
for testing and result in more robust code
using SQLite. To amuse yourself try doing a natrual join (sic) sometime!
Sadly the SQLite team rejected it:
http://www.sqlite.org/src/tktview?name=25e09aa2ab
Roger
___
sqlite-users mailing list
sqlite-users
to be structured,
managed by the operating system and to be record based with file apis
working that way. Unix turned files (and similar) into unstructured bags of
bytes.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin
, all it takes is some changes in the future to
invalidate that.
I strongly recommend not playing with fire.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
be using a recent version of SQLite which will have more defensive
code in it based on real world experience.
http://rogerbinns.github.io/apsw/pysqlite.html
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman
/redo
would be helpful. Suggesting a thumbnail entry is good too, etc.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On 07/09/14 05:20, Joe Mucchiello wrote:
So I'm posting it here.
For the record, this wiki page explains how to report a SQLite bug (first
google result too):
https://www.sqlite.org/src/wiki?name=Bug+Reports
Your issue is covered in the FAQ.
Roger
)size_t. This could be handled like how the UNIX world introduced
64 bit file sizes and offsets, using the preprocessor to point at the
appropriately sized routines for aware code.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org
than 2GB, and then the warning can be silenced in a
cast.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
/wal.html
Realise that SQLite can only be safe if at various points the data it wants
on the storage is actually completely written out and unaffected by power
failures etc. You can go a lot faster by not doing that, but then the data
isn't safe.
Roger
. Chances are that is
actually what is happening in your case.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
. However you will be better off structuring
your code so you don't need to know that information up front.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
talloc.
As for the effort thinking about this, and posting about it:
http://c2.com/cgi/wiki?PrematureOptimization
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
easier.
https://developer.apple.com/technologies/ios/data-management.html
I recommend you use Core Data unless you can show it won't meet your needs
and you need to use SQLite. (BTW Core Data uses SQLite behind the scenes.)
Roger
___
sqlite-users
)
That has no connection to APSW either. It is written by someone else to
turn rows returned from a tuple into also having the column names.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo
, timezone) are picked up from their
browser and OS preferences.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
preferences from the operating system they run on which in turn
is based on user preferences.
There is no need for timezones even for your example. Displaying the
timestamp relatively solves that (eg 13 hours ago).
Roger
___
sqlite-users mailing list
sqlite
is annoyingly hard, which the
relative value caters for.
The developer/product manager can work out what is most appropriate for
their users - eg showing only relative times, full with tooltip as relative,
both relative and full etc. But yeah, this is formatting.
Roger
#pragma_temp_store
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlPIH8wACgkQmOOfHg372QRtLwCfYUzGhB4UKejmTT0qcVRRHNQy
bRgAn2MdaOspER3bgVcwlgKjLq3G8akr
=B7gd
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http
/tips.html#diagnostics
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlPFX04ACgkQmOOfHg372QT16gCgoHzHNaGCVAYwxBfu79iXuRt6
B7gAoJY5RX9MCgimDCSeloiXnNrZncgZ
=uqmR
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users
to close the string.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlPETsAACgkQmOOfHg372QSdhgCgpYdrerB7nrE2F+tqRushIScm
3o0AoLLC9djTNUb9Kx4V75GJpHeF9Hl3
=2TNc
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/14 22:51, Manoj wrote:
Is there any workaround available for this?
https://sqlite.org/limits.html#max_column
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlO8B14ACgkQmOOfHg372QRr6QCfZfbcFkz/lowVT8uBFy92FY/7
fEAAn1
into one potential solution.
For example the authorizer API can be used to find out exactly which
columns a statement modifies.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlO8Cd8ACgkQmOOfHg372QTSfQCfZHzBbpJiI5ollGT8xhbX7YVH
oHcAoM6KLJ+uYsS0r7lB3vxAPBkmc9pk
=Zzor
-END PGP
://github.com/rogerbinns/apsw/issues/166
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlOtuEwACgkQmOOfHg372QSw6gCeKZ6qQrsnyWiFcRNZTgxxdI40
CQIAoJxp4Z6kzFQKWyEQHFr0R2sFY0xa
=dWYR
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite
, or prevent/replace with null certain columns.
https://sqlite.org/c3ref/set_authorizer.html
That page doesn't give any examples of what you see. The doc for my
python SQLite wrapper shows three examples:
http://rogerbinns.github.io/apsw/example.html#authorizer-example
Roger
-BEGIN PGP
://sqlite.org/th3.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlOpHNMACgkQmOOfHg372QQEZACeIlRc/4JICpbQNbajdWfTlffr
0WUAoMRjzQcDTpz9PHGWk5oxrpRauwX/
=paUV
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/06/14 13:02, Dave Wellman wrote:
I have some rows in a table (not very many, typically less than 20) and
I want to generate a unique, sequential number for each row.
http://www.sqlite.org/autoinc.html
Roger
-BEGIN PGP SIGNATURE
for the foreseeable
future, extra scripting stuff would be added.
It is far more sensible to use an existing one than invent an arbitrary
new one.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman
. This means you
don't need to worry about DLL hell or similar issues. It is exactly one
file and hence far less to go wrong.
- or more simply, they can't install anything on their school PC.
You don't actually need to install - you just need that one file (apsw.so
or .pyd).
Roger
-BEGIN PGP
/attachments/319_PGCon2014OpeningKeynote.pdf
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlOM5koACgkQmOOfHg372QT3mgCgmwr+WK2ELill/G01GKUgmUIq
paYAniQO7MH2Wx5hjmn3wJTl1Ja67Xq1
=FY2G
-END PGP SIGNATURE-
___
sqlite-users mailing
you should manually do the transaction
boundaries yourself.
pysqlite implements the DBAPI semantics by parsing supplied SQL and does
occasionally get outwitted. APSW just lets SQLite do its thing.
http://rogerbinns.github.io/apsw/pysqlite.html
Roger
), or by internal compression with cerod:
http://www.hwaci.com/sw/sqlite/cerod.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlOFpvsACgkQmOOfHg372QRSRACfcDqTprcD//n9yYXcGPl9yQfo
sTIAoLkIaQHR4JAwk1LbuRzCyQsx/5aN
=tYeT
-END PGP SIGNATURE
to measure and tweak multiple places.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlOGMfgACgkQmOOfHg372QT9IACfVvhc1LWG4X2IFBC0rKKNnrdw
UFIAoNhtFdh1EZKEo3fx7Kj9bkdKJRW4
=02fs
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite
://www.sqlite.org/src/tktview?name=25e09aa2ab
The SQLite team rejected it in March.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlN/2XsACgkQmOOfHg372QRtnACeOCNixsgztnpZSqk/4T4fWqZE
fN4An0t4mC2VQOXwXeCnV3qYrUTULHRx
=qk0x
-END PGP SIGNATURE
representation,
and inside because statement preparation takes a while - it involves
parsing, many memory allocations and lots of other fiddly stuff.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlN7rRMACgkQmOOfHg372QRVoQCgtNdWJ/LiD67W2O7sdVSGinbV
mvQAniz4mbJr3+8pzYj0siG5v
.
There is a ticket including pointers to previous mailing list discussion:
http://www.sqlite.org/src/tktview?name=ee4b2b48f5
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlN6dfEACgkQmOOfHg372QQmcACfX46ZvXwKt/Y9DnBL0BRxH9QM
lFsAoLRh/hjZai4SC5ie/DCpd2+D3NA2
=1Ve9
-END PGP SIGNATURE
of the SQL statement.
SQLite already has to deal with all these issues, including keeping a
copy of the statement so SQLite implementing the cache would save memory.
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi
.
SQLite could provide the information as a virtual table or similar. A
ticket was created 7 years ago asking for it, and closed 2 months ago by
the team with resolution Rejected:
https://www.sqlite.org/src/tktview?name=5896edbe46
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
to understand your data shape and queries.
There was a now defunct project UnQL that was mixing together JSON like
data, SQL like queries and bit of SQLite.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlNW19UACgkQmOOfHg372QTNvgCgltU2vNzzVuRfTuPdc2+59VXS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/04/14 15:00, Neville Dastur wrote:
On 22 Apr 2014, at 21:58, Roger Binns rog...@rogerbinns.com wrote:
Your data is from MongoDB :) Note they do have an extended JSON to
deal with types like ObjectId, binary and dates:
Yes, it is. But I
example where you created
another view of the same name. (There are some other edge cases where you
could create circular links between views.)
I can't see any way of resolving your issue since there is no general SQL
parser which is what would have to be run to work out dependency order.
Roger
being used was not visible (nor relevant) to the
user. This approach worked fine on Windows, Linux and Mac.
[1] distutils - a standard part of python - is used under the hood which
has multiple subcommands each of which can be given flags. pip etc
ultimately call into that.
Roger
-BEGIN PGP
for.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlMvwWMACgkQmOOfHg372QSnOQCdEpBWBvcNsntkZ6WPvDs0yAju
fc0AoJzagj56DyoYrhmeE73rwHhe+D2f
=ZAfw
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users
. There was
a feature request ticket for several years for checksums to at least catch
unexpected changes to the data itself:
https://www.sqlite.org/src/tktview?name=72b01a982a
Sadly it was rejected a few weeks ago without explanation.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU
code including any
code that calls that code, to audit for overflows, to provide a new api
and tests for that.
And to ensure that stays maintained for the future lifetime of SQLite 3.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux
it by having a setup that doesn't have failures such as
using battery backup.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlMUxBMACgkQmOOfHg372QTxewCgjuqKWh4m+pz2JRtQWznPA83o
YEcAnjDuMMULpMX14VVlLsQ4NmJbD6PA
=Dp0Y
-END PGP SIGNATURE
http://catb.org/~esr/faqs/smart-questions.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEUEARECAAYFAlMSPxoACgkQmOOfHg372QQXIQCfT7Sa9kempGXWTYs+L6aot98I
Rw8AmJ2dp9jR0bN0FThp98ab/ZygeD0=
=T0I3
-END PGP SIGNATURE
greatly appreciate it I think the file ext. is a plist. Live, love
laugh.
In addition to those, read this:
http://catb.org/~esr/faqs/smart-questions.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlMRNzgACgkQmOOfHg372QTAWACglwFrY79O3Z8U0Hz7xCv3B8VM
have. It also supports very old versions of
SQLite - I believe it will work correctly with 3.0.0!
If we wish to have SQLite + Python combination
You'll find the python sqlite community at
https://groups.google.com/forum/#!forum/python-sqlite
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG
/data in flight.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlLYT00ACgkQmOOfHg372QTw3QCfQNoOjJHrs9+pTSNmAx5BCoXk
essAoM0wmW454CL54bf0u2XTqV9vNxXP
=DY1e
-END PGP SIGNATURE-
___
sqlite-users mailing list
. The blocking thread could have
finished after 10ms, but you'll still be stuck in the busy handlers for
another 990ms.
Simply ensure HAVE_USLEEP is defined when building sqlite3.c. Or add your
own busy handler that sleeps for sub-second amounts of time.
Roger
-BEGIN PGP SIGNATURE
that SQLite should have a statement cache built in
rather than everyone having to implement their own:
https://www.sqlite.org/src/tktview?name=ee4b2b48f5
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlLB3aYACgkQmOOfHg372QSsFgCgwLkmzGqOrVL9YRLy6gG1E/cC
W
nonsense and 0;
0
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlKzo/8ACgkQmOOfHg372QTyVACfbNlMOQR5nxfzgUg7tY5pF8il
d0sAnjIp9K/aAIFXZcbc+pZvDdK6tN0x
=Siia
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite
since you last looked at the file.
You can use a trigger internally at the SQL level to track changes in a
meaningful way too.
Finally you can disable the use of memory mapping - have a look at the
Windows VFS.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux
to at least make
detecting a mismatch between the database and a (possibly non-existent)
journal possible:
https://www.sqlite.org/src/tktview?name=61d35ac210
Roger
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin
://musicbrainz.org/doc/MusicBrainz_Database/Schema
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJ8ZWQACgkQmOOfHg372QQN/wCg0EyCpIs8pl9MVOzerfshJKxc
JwAAoN+E6Wa8T3zWZ+r5ghLpeK1a8dem
=23xE
-END PGP SIGNATURE-
___
sqlite
the SQLITE_BUSY
error code.
On Android I use the SQLiteDatabase class, and the insert method it
provides and haven't encountered this issue.
https://developer.android.com/reference/android/database/sqlite/SQLiteDatabase.html
How are you inserting the data?
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG
/Context.html#getCacheDir()
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJTb3YACgkQmOOfHg372QTbUwCguSVoQ7AcJrGCk7qwwhzFQOqQ
z5YAoIFNQxhOTeP8/0Aq2lEpOD0Lc+GT
=VUgP
-END PGP SIGNATURE-
___
sqlite-users mailing
likes to do that). As another bonus
it is also a bit faster too as the compiler ends up inlining SQLite code
into your methods that call it.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJCBoIACgkQmOOfHg372QRRsQCePzIDcnfYiXf3c/RHyqhnlsdz
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJCZOcACgkQmOOfHg372QRaYwCgqoR4C9DmXg27SCbOXg2a4GNe
vyUAnRYFf8Uej21hrJTkhwXJWddkvYWi
=bKyX
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users
column for each title.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlI/3EAACgkQmOOfHg372QSuHgCgla77zTSx5knJL036AMpU0Unx
JnEAoJ9Cx/kocO3ue4xafKFkM7BVEviE
=RDic
-END PGP SIGNATURE-
___
sqlite-users mailing
whatever
it deems necessary to gather to make the query perform well in the future.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIyQagACgkQmOOfHg372QT8jgCgtSROjcL1dyrHo+yP2leh1ffV
xBEAoKEOTIVqz3vlrVrlVeJ130Wru/Mg
=+8TU
-END PGP SIGNATURE
with transactions, and starts them behind your back.
That is possibly causing problems for you too.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIk8J8ACgkQmOOfHg372QTYCQCgi79D27GRMc6Tgjc8a+lI0Gt2
7IUAoOHGHlTKTJDmle82l5d98nWozmJ8
=PA/r
-END PGP SIGNATURE
sequences of api calls.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIj0AIACgkQmOOfHg372QTU5QCfeGcle8r3m8nDs3dDgI7zb6BK
qWQAoLWkeKarpubX4S1SzcBxaT5LT1yr
=sjZY
-END PGP SIGNATURE-
___
sqlite-users mailing list
is similar to pysqlite, but not the same. It
behaves the SQLite way rather than the DBAPI way.
http://apidoc.apsw.googlecode.com/hg/pysqlite.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIj0vYACgkQmOOfHg372QSYrwCcCuJyMqsUiS5SYVFpeYll72d
this for several years.
http://www.sqlite.org/src/tktview?name=c060923a54
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIXpJkACgkQmOOfHg372QQDFQCgn56WYKUg3oxbiZ0Kp886flWa
H+sAoLMWH6Q462K1Lb5pTs7WwlZyxlnf
=Uj9e
-END PGP SIGNATURE
out to be the least exercised
part of protocols and where bugs/quirks lie.
[1] http://www.rogerbinns.com/visionfs.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIMB3wACgkQmOOfHg372QTyGgCgxB/7XxUibw+p0T/aI0cNecE4
ZegAoMDoh7RKb6hZmXsWTbreWhXpSYWP
=0UbL
also generate arbitrary
messages.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlIIrLsACgkQmOOfHg372QS2pACeK5gt9bOdk9dX3gM+kxhYt6xA
MxQAnRLb4yMHdNEV6RpV0MbFUQVteNJ/
=gJrr
-END PGP SIGNATURE-
___
sqlite-users
from
sqliteman.
Attachments get stripped from the mailing list. You can put them
somewhere like Dropbox.
Did you run analyze?
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlICmtMACgkQmOOfHg372QSRLwCgkb0vJAQ/cnH+nr85W2PUJJrY
U0kAoOPseXJlXtSqJw95tNgq1RUMHp37
1 - 100 of 1421 matches
Mail list logo