QofBackend / QofSession changes in next commit.

[Derek Atkins]

Mostly I'm thinking about how we upgrade users from xml -> SQLite..  
I'd prefer
to not require user intervention to convert to the new format.  But perhaps we
should?  I don't know.

-derek

Quoting Neil Williams <linux at codehelp.co.uk>:

> On Tuesday 30 August 2005 11:30 pm, Derek Atkins wrote:
>> This sounds reasonable to me...  And will solve the SQLite issue --
>> the only question is: how do we "order" be backends so that we can
>> get certain types in preference to others?  In particular for
>> File -> SaveAs
>
> Good question - first thoughts are:
>
> 1. Keep to the same backend to write as was used to load where possible.
>
> 2. Use markers in the QofBook (like partial books) where necessary /
> supported.
>
> Other situations will need a formal QofSession call - if the
> QofBackendProvider list is made readable (maybe a foreach) and/or if the
> SaveAs routines pass the ID/name of the selected QofBackendProvider to a new
> function:
> qof_session_change_backend(QofSession *, const char *backend_provider_name);
> or
> qof_session_change_backend(QofSession *, QofBackendProvider *);
>
> This should probably allow changing the access_method at the same time.
>
> I'll look into it.
>
> --
>
> Neil Williams
> =============
> http://www.data-freedom.org/
> http://www.nosoftwarepatents.com/
> http://www.linux.codehelp.co.uk/
>
>



-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available