Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On Thu, 2013-07-11 at 17:22 +0200, Lionel Elie Mamane wrote:
t seems to bring more
problems than it is worth.

Makes sense. I still need to figure out how to do this given I'm
dealing with the storage within the driver, and the driver currently
doesn't get told when the .odb is being saved.

My first guess is: it registers as a listener for that event.

http://api.libreoffice.org/docs/common/ref/com/sun/star/document/XDocumentEventBroadcaster.html
http://api.libreoffice.org/docs/common/ref/com/sun/star/sdb/OfficeDatabaseDocument.html#XDocumentEventBroadcaster

If that cannot work for some reason, then stick embedded-specific code
in the code path of "save odb file".

That works (I've not quite implemented the actual saving yet but the event
arrives as expected). If I understand things correctly there's 1 connection per
odb that is open (i.e. all the embedded specific work can be done in
FConnection)?

(For the moment I'm just copying the .fdb file and will add code
to ensure a safe state of the file once that's working.)

Also, libfbembed is supposed to support connecting to remote firebird servers
-- I guess it's worth eventually supporting this too (as far as I can tell
the only thing I'd need to add is support for username/password/url, although
those can probably be done manually as part of the connection string)?

Cheers,

        Andrzej


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.