On Fri, Jun 28, 2013 at 11:37:15AM +0200, Jean-Pierre Ledure wrote:
As a conclusion, might I suggest that a bit automation facilitating
a clear initial choice for a new database between embedding or not
embedding data could be appreciated by users ?
What kind of automation do you have in mind? Something that creates
the external (empty) database, and sets up an .odb file to connect to
it, all in one wizard? That could be good, yes.
Anything that makes user's life easier / better is good; we take
patches :)
Not embedding would simply mean that data files shall be stored in
the same directory as the database document (.odb) and that the
directory as a whole should be considered as the database.
Interesting idea. This allows some level of transportability (no
hardcoded path in the .odb), will be more robust and probably
faster. It needs some kind of file-based (as opposed to server-based)
database "obviously". We may have to pass an absolute path to the
DBMS layer, but we can ~easily construct that from the path to the
.odb file.
My first thought would be to name the database file(s) with the same
base name as the .odb file, so that there can be several such .odbs in
a directory.
I'd be happy to see patches to implement this concept.
--
Lionel
Context
Re: LO / Firebird DB Integration · Michael Meeks
Firebird ICU/binary compatibility · Lionel Elie Mamane
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.