On 1/31/2015 12:21 AM, Godmar Back wrote:
If I want to do a dump of the table, as in "SELECT value FROM " I'll
quickly get "database is locked" errors. Googling revealed that those are
because a long running select keeps a cursor, and thus readlock on the
entire database. I have since
Thank you very much for those suggestions!
Select max(rowid) completes immediately, I haven't tried WAL mode and the
idea of sorting yet.
https://www.sqlite.org/wal.html appears to be down right now, but
http://www.sqlite.org/wal.html is up.
On Sat, Jan 31, 2015 at 5:31 AM, Igor Tandetnik
1. No client-server, I use MySQL, SQL-Server or ORACLE for that.
2. No access to the SQLite database ever by more than one process concurrently
in writable mode. In readable mode, yes. But the reported damage cases were
always single user, one PC.
3. I cannot prevent or disallow users to
As I wrote above, damaged databases are replaced. No user continues working
with a damaged database once it has been identified. The issue here is to
detect this early and avoid it altogether.
> One column of one row of one table may get corrupted.
> If that's the case then the database
On 1/31/15, Godmar Back wrote:
> Thank you very much for those suggestions!
> Select max(rowid) completes immediately, I haven't tried WAL mode and the
> idea of sorting yet.
> https://www.sqlite.org/wal.html appears to be down right now, but
We've just released v3.5.0 of DB Browser for SQLite:
This release has a fair amount of bug fixes (eg in CVS import), plus
several usability tweaks, and now supports Simplified Chinese.
This is the first release to
On Fri, 30 Jan 2015 13:17:26 -0500
Stephen Chrzanowski wrote:
> 2.1 Filesystems with broken or missing lock implementations
> SQLite depends on the underlying filesystem to do locking as the
> documentation says it will. But some filesystems contain bugs in their
On Fri, 30 Jan 2015 10:39:31 +0200
> At first I thought SQLite (or any RDBMS) should really strore
> whatever you give and return it untouched, but that cannot be true
> for an RDBMS because it has to interpret the data, it isn't just a
> binary store. It has to
On 31 Jan 2015, at 11:14pm, James K. Lowden wrote:
> That said, https://www.sqlite.org/datatype3.html says REAL is "stored
> as an 8-byte IEEE floating point number". I can't see why a
> non-signalling NaN couldn't be stored and interpreted. You'd need some
On Sun, Feb 1, 2015 at 2:07 AM, Simon Slavin wrote:
> So, having established that NaN and -0 do not make the round trip from a C
> variable through a database and back into a C variable ... at least I think
> we have ...
If you're assuming C89 (which sqlite3 is, by and
Mail list logo