PIM/MS Windows/SQLite Folder Indices: Difference between revisions
< PIM | MS Windows
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
==KMFolderIndex== | ==KMFolderIndex== | ||
[http://api.kde.org/4.x-api/kdepim-apidocs/kmail/html/classKMFolderIndex.html api docs] | |||
*2008-04-23 | *2008-04-23 | ||
**mIndexId unused - removed as well as serialIndexId() | **mIndexId unused - removed as well as serialIndexId() | ||
| Line 12: | Line 13: | ||
==KMMsgBase== | ==KMMsgBase== | ||
[http://api.kde.org/4.x-api/kdepim-apidocs/kmail/html/classKMMsgBase.html api docs] | |||
*2008-04-23 | *2008-04-23 | ||
**move syncIndexString() to KMFolderIndex, where we can impleemnt it for SQLite differently | **move syncIndexString() to KMFolderIndex, where we can impleemnt it for SQLite differently | ||
Revision as of 09:39, 23 April 2008
There are issues with locking index files for KMail folders and mmap()/munmap() operations on Windows. Therefore, SQLite-based indices are in development. This page presents detailed development notes for this task.
Started: jstaniek 11:35, 23 April 2008 (CEST)
KMFolderIndex
- 2008-04-23
- mIndexId unused - removed as well as serialIndexId()
- indexLocation(): added .db suffix to indicate the index is sqlite-based
- INDEX_VERSION is written and checked using 'PRAGMA user_version = <integer>' command [1]
- we do not use temporary filenames, e.g. in writeIndex(): SQLite takes care about safe storage
- updateIndex() no changes, we're changing implementation of KMMsgBase::syncIndexString() and writeIndex() instead
KMMsgBase
- 2008-04-23
- move syncIndexString() to KMFolderIndex, where we can impleemnt it for SQLite differently
Status of porting to SQLite
| TOPIC | PORTED | TESTED | NOTES |
|---|---|---|---|
| KMFolderIndex:indexLocation() | yes | added .db suffix to indicate the index is sqlite-based |