Re: [sqlite] New 3.7.0 snapshot - release estimated for July 22
On Wed, Jul 14, 2010 at 2:12 PM, D. Richard Hipp wrote:
> The signature of the VFS has changed slightly - the xShmOpen() method
> has been removed. Implementations are now expected to automatically
> create the shared memory on the first call to xShmMap(). And the
> xShmClose() method has been renamed to xShmUnmap(). A new snapshot
> with these changes is now available in the usual place:
>
>
I also see that the order of two methods (Lock and map) was changed. No
problem, just checking is it correct
struct sqlite3_io_methods {
(201007091257)
int (*xShmOpen)(sqlite3_file*);
int (*xShmLock)(sqlite3_file*, int offset, int n, int flags);
int (*xShmMap)(sqlite3_file*, int iPage, int pgsz, int, void volatile**);
(201007140820)
int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**);
int (*xShmLock)(sqlite3_file*, int offset, int n, int flags);
Max
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] New 3.7.0 snapshot - release estimated for July 22
The signature of the VFS has changed slightly - the xShmOpen() method has been removed. Implementations are now expected to automatically create the shared memory on the first call to xShmMap(). And the xShmClose() method has been renamed to xShmUnmap(). A new snapshot with these changes is now available in the usual place: http://www.sqlite.org/draft/download.html The target release date for version 3.7.0 has slipped until 2010-07-22 (a slip of one week). We were going to try to revise WAL so that it worked as a read-only database if write permission to key files was not available. But that was going to turn out to be a big, error- prone mess, and so we decided to back off and simply make it a limitation of WAL that a database could not be read or written in WAL mode if write permissions were lacking. Additional explanation at http://www.sqlite.org/draft/wal.html#readonly The documentation has also been enhanced (in a subsection immediately following the section on read-only databases linked above) to explain our decision to implement shared-memory using a mmapped file in the same directory as the original database. Comments and criticism of this decision are encouraged. Please evaluate the snapshot and provide feedback on this mailing list. The 2010-07-22 release date target assumes no more major problems. But we would rather encounter (and fix) a major problem before the release rather than afterwards. We will slip the release again if necessary. Your beta testing is *very* important. Thanks! D. Richard Hipp d...@hwaci.com ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
