Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Minor correction to the 3.7.13 news. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
78b3be0bd91102aaf082d0d6076a7779 |
User & Date: | drh 2012-06-14 17:04:32.778 |
Context
2012-06-17
| ||
23:53 | Fix an issue with the chroot jail. At the ability to 404 certain Referer values. (check-in: cf0aea0254 user: drh tags: trunk) | |
2012-06-14
| ||
17:04 | Minor correction to the 3.7.13 news. (check-in: 78b3be0bd9 user: drh tags: trunk) | |
12:44 | Add WinRT and 64-bit binaries to the download page. (check-in: 7dda75edf9 user: drh tags: trunk) | |
Changes
Changes to pages/news.in.
︙ | ︙ | |||
24 25 26 27 28 29 30 | applications for Microsoft Windows 8. The 3.7.13 release is coming sooner than is usual after the previous release in order to get this new capability into the hands of developers. To use SQLite in a metro style application, compile with the -DSQLITE_OS_WINRT flag. Because of the increased application security and safety requirements of WinRT, all database filenames should be full pathnames. Note that SQLite is not capable | | | | 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 | applications for Microsoft Windows 8. The 3.7.13 release is coming sooner than is usual after the previous release in order to get this new capability into the hands of developers. To use SQLite in a metro style application, compile with the -DSQLITE_OS_WINRT flag. Because of the increased application security and safety requirements of WinRT, all database filenames should be full pathnames. Note that SQLite is not capable of accessing databases outside the installation directory and application data directory. This restriction is another security and safety feature of WinRT. Apart from these restrictions, SQLite should work exactly the same on WinRT as it does on every other system. Also in this release: when a database is opened using [URI filenames] and the [coreqp | mode=memory] query parameter then the database is an in-memory database, just as if it had been named ":memory:". But, if shared cache mode is enabled, then |
︙ | ︙ |