Age | Commit message (Collapse) | Author | Files | Lines |
|
Each Backend can:
-Sort and Filter a set of Records/AllRecords (which can be filtered again)
-QueryByExample by every Backend
-Occurrences for a period of time and a QDateTime
-More common implementation
-OPimBackendOccurrence with common splitting to OPimOccurrence
|
|
|
|
|
|
|
|
Changing API: Default now gets a OPimGlobal::PimType as first param instead of QString.
|
|
because QString::null is not in the dictionary of available backends.
I'm conversative so it is 'xml'
Eilers/BradC change it on your will
|
|
Changing OBackendFactory::Default to defaultBackend
I hope this fixes all problems with reserved words.. Sorry for any
inconveniences..
|
|
|
|
by Settings/pimaccess.conf.
This will be used by the OPimAccessFactory .. see next commit..
|
|
It is still very basic but simplifies the access of the pim database and covers
the creation process itself..
The new class OPimGlobal will contain constants and enums which should be
public available for users of the PIM-classes..
|
|
but that will be not visible to application classes so we can change it later.
|
|
someone should take a look for a better file order. but now all applications can start using libopiepim2 instead of libopie1-pim-stuff.
|
|
port the PIM datebook application to use it, before I could debug the
whole stuff.
Thus, PIM-Database backend is finished, but highly experimental. And some
parts are still generic. For instance, the "queryByExample()" methods are
not (or not fully) implemented. Todo: custom-entries not stored.
The big show stopper: matchRegExp() (needed by OpieSearch) needs regular
expression search in the database, which is not supported by sqlite !
Therefore we need either an extended sqlite or a workaround which would
be very slow and memory consuming..
|
|
Some modifications to be able to compile the todo sql-backend.
A lot of changes fill follow...
|
|
|
|
QString -> const QString&
QString = 0l -> QString::null
|
|
-clean up todoaccessxml header
-implement some more stuff in the oeven tester
-extend DefaultFactory to not crash and to use datebook
-reading of OEvents is working nicely.. saving will be added
tomorrow
-fix spelling in ODateBookAcces
|
|
|
|
I tested it with my todolist and it 'works' for 10.000 todos the hits are awesome ;)
The read ahead functionality does not make sense for XMLs backends because most of the stuff is already in memory. While using readahead on SQL makes things a lot faster....
I still have to fully implement read ahead
This change is bic but sc
|
|
The SQL-Stuff is currently deactivated. Otherwise everyone who wants to
compile itself would need to install libsqlite, libopiesql...
Therefore, the backend currently uses XML only..
|
|
|