Roger,
please remember to do group-replies.
On Mi, 2011-08-24 at 01:39 +1000, Roger KeIrad wrote:
To solve to the DB schema problem, it will be usefull to implement a
rapper that can be used by anyone who would like to synchronize using
sqlite backend. when the DB schema change only the rapper will
change .
My expectation is that the Synthesis sqlite datastore has a
configuration mechanism. Whether it covers the relevant mapping in this
case would have to be investigated.
can you explain to me what's the iCalendar import/export
mechanism ?
See MAKE/PARSETEXTWITHPROFILE() and how SyncSource uses it.
what 's the part that ensure the mapping from some higher-level
representation of calendar data to the schema ?
The mapping between the internal field list (which is kind of
higher-level) and the iCalendar text format is done via profiles. See
http://syncevolution.org/development/pim-data-synchronization-why-it-so-hard
How it is done with direct sqlite access I don't know. I have never used
or investigated that part. See SySync_config_reference.pdf and search it
for SQL.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.