[sqlite] sqlite3 command line, read-only

https://www.sqlite.org/wal.html "5. It is not possible to open read-only WAL databases. The opening process must have write privileges for "-shm" wal-index shared memory file associated with the database, if that file exists, or else write access on the directory containing the database file if

[sqlite] sqlite3 command line, read-only

On Apr 26, 2016 8:16 PM, "Mark Foley" wrote: > > I'm back with more read-only issues. > > Thanks to postings on this list, I've made progress, but still more issues. > > Using the sqlite3 command-line, I'm attempted to open, > read-only, a database located on a Windows 7 workstations, from a

[sqlite] sqlite3 command line, read-only

I'm back with more read-only issues. Thanks to postings on this list, I've made progress, but still more issues. Using the sqlite3 command-line, I'm attempted to open, read-only, a database located on a Windows 7 workstations, from a Linux server. I am mounting the Windows volume r/o: mount

[sqlite] SQLite SEE with FIPS compliant Encryption?

On 4/26/16, Mike Nicolino wrote: > Hello Everyone, > > We're using SQLite SEE to encrypt our databases and I was wondering if there > is a version of SEE that is FIPS compliant/certificated? If you will read FIPS 140-2, you will find that it has many requirements that are outside the purview of

[sqlite] No datasize field - why?

Scott wrote: >It depends on what you call a character. If you consider a "character" the >same way most people do (one typographical unit), then you have to deal >with varying numbers of code points per character, even in a "fixed width" >encoding like UTF-32. There is no hard limit on how many