亚洲免费在线-亚洲免费在线播放-亚洲免费在线观看-亚洲免费在线观看视频-亚洲免费在线看-亚洲免费在线视频

In-Memory Databases

系統(tǒng) 1788 0

In-Memory Databases

In-Memory Databases

An SQLite database is normally stored in a single ordinary disk file. However, in certain circumstances, the database might be stored in memory.

The most common way to force an SQLite database to exist purely in memory is to open the database using the special filename " :memory: ". In other words, instead of passing the name of a real disk file into one of the sqlite3_open() , sqlite3_open16() , or sqlite3_open_v2() functions, pass in the string ":memory:". For example:

        rc = sqlite3_open(":memory:", &db);

      

When this is done, no disk file is opened. Instead, a new database is created purely in memory. The database ceases to exist as soon as the database connection is closed. Every :memory: database is distinct from every other. So, opening two database connections each with the filename ":memory:" will create two independent in-memory databases.

The special filename ":memory:" can be used anywhere that a database filename is permitted. For example, it can be used as the filename in an ATTACH command:

        ATTACH DATABASE ':memory:' AS aux1;

      

Note that in order for the special ":memory:" name to apply and to create a pure in-memory database, there must be no additional text in the filename. Thus, a disk-based database can be created in a file by prepending a pathname, like this: "./:memory:".

The special ":memory:" filename also works when using URI filenames . For example:

        rc = sqlite3_open("file::memory:", &db);

      
Or,
        ATTACH DATABASE 'file::memory:' AS aux1;

      

In-memory Databases And Shared Cache

In-memory databases are allowed to use shared cache if they are opened using a URI filename . If the unadorned ":memory:" name is used to specify the in-memory database, then that database always has a private cache and is this only visible to the database connection that originally opened it. However, the same in-memory database can be opened by two or more database connections as follows:

        rc = sqlite3_open("file::memory:?cache=shared", &db);

      
Or,
        ATTACH DATABASE 'file::memory:?cache=shared' AS aux1;

      

This allows separate database connections to share the same in-memory database. Of course, all database connections sharing the in-memory database need to be in the same process. The database is automatically deleted and memory is reclaimed when the last connection to the database closes.

If two or more distinct but shareable in-memory databases are needed in a single process, then the mode=memory query parameter can be used with a URI filename to create a named in-memory database:

        rc = sqlite3_open("file:memdb1?mode=memory&cache=shared", &db);

      
Or,
        ATTACH DATABASE 'file:memdb1?mode=memory&cache=shared' AS aux1;

      

When an in-memory database is named in this way, it will only share its cache with another connection that uses exactly the same name.

Temporary Databases

When the name of the database file handed to sqlite3_open() or to ATTACH is an empty string, then a new temporary file is created to hold the database.

        rc = sqlite3_open("", &db);

      
        ATTACH DATABASE '' AS aux2;

      

A different temporary file is created each time, so that just like as with the special ":memory:" string, two database connections to temporary databases each have their own private database. Temporary databases are automatically deleted when the connection that created them closes.

Even though a disk file is allocated for each temporary database, in practice the temporary database usually resides in the in-memory pager cache and hence is very little difference between a pure in-memory database created by ":memory:" and a temporary database created by an empty filename. The sole difference is that a ":memory:" database must remain in memory at all times whereas parts of a temporary database might be flushed to disk if database becomes large or if SQLite comes under memory pressure.

The previous paragraphs describe the behavior of temporary databases under the default SQLite configuration. An application can use the temp_store pragma and the SQLITE_TEMP_STORE compile-time parameter to force temporary databases to behave as pure in-memory databases, if desired.

In-Memory Databases


更多文章、技術交流、商務合作、聯(lián)系博主

微信掃碼或搜索:z360901061

微信掃一掃加我為好友

QQ號聯(lián)系: 360901061

您的支持是博主寫作最大的動力,如果您喜歡我的文章,感覺我的文章對您有幫助,請用微信掃描下面二維碼支持博主2元、5元、10元、20元等您想捐的金額吧,狠狠點擊下面給點支持吧,站長非常感激您!手機微信長按不能支付解決辦法:請將微信支付二維碼保存到相冊,切換到微信,然后點擊微信右上角掃一掃功能,選擇支付二維碼完成支付。

【本文對您有幫助就好】

您的支持是博主寫作最大的動力,如果您喜歡我的文章,感覺我的文章對您有幫助,請用微信掃描上面二維碼支持博主2元、5元、10元、自定義金額等您想捐的金額吧,站長會非常 感謝您的哦!!!

發(fā)表我的評論
最新評論 總共0條評論
主站蜘蛛池模板: 免费播放美女一级毛片 | 伊人久久综合视频 | 久草免费在线观看视频 | 99久久国产综合精品女小说 | 国产三级观看久久 | 久久综合图区亚洲综合图区 | 精品久久久一二三区 | 亚洲精品一区二区三区香蕉在线看 | 毛片爱爱 | 欧美日韩亚洲一区二区 | 成人9久久国产精品品 | 一级一级一级毛片免费毛片 | 精品国产免费久久久久久婷婷 | 97视频久久久 | 中文字幕在线观看一区 | 精品国产一区二区三区四区不 | 好吊妞乱淫欧美 | 欧美成一级 | 久热最新| 五月婷影院 | 久久久久久a亚洲欧洲aⅴ | 色片在线观看 | 羞羞视频网页 | 亚洲性片 | 亚洲视频在线一区 | 夜夜干天天操 | 49xxx中国妇女内谢视频 | 免费观看一级特黄欧美大片 | 亚洲涩综合 | 伊香蕉大综综综合久久 | 99爱这里只有精品 | 国产精品久久久久无毒 | 亚洲欧美一区二区三区在线 | 99精品国产久热在线观看66 | 久久97精品久久久久久久看片 | se999se男人最爱 | 久久精品国产999久久久 | 亚洲综合网站 | 国产一区二区不卡免费观在线 | 91婷婷色 | 久久久久亚洲 |