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


Hi :)
No, the problem is much larger, as Owen states.

Data-loss is a very serious issue, especially in a database!!

Of course documentation tries to keep things as simple as possible!
Learning just enough about databases in order to create one is FAR more
difficult than learning just enough to use Writer/Word or Calc/Excel.  It
is POSSIBLE to create a database using the internal back-end and from there
the tables can be moved into a back-end if you are not happy about losing
data.


The version of HsqlDb that is used as a back-end right now is NOT a fair
representation of HsqlDb itself.  The one in the back-end doesn't update
and was heavily tweaked.  It is NOT just because it's dependant  on Java.

People who get the proper HsqlDb from it's own project's website and use it
as an external back-end tend to report seeing a vast improvement in quality
and none of the problems the internal one has.

When all the tweaks were put in place it was probably due to pressure to
force Base to act in a way it wasn't originally designed to be used in
order to be as limited as MS Access.


LO devs are working at replacing the in-built one with a more pure version
of something else.  Presumably this time making it easier to upgrade.
Regards from
Tom :)




On 5 July 2014 18:06, Dale Erwin <dale.erwin@casaerwin.org> wrote:

On 7/4/2014 11:40 PM, Owen Genat wrote:

NoOp wrote

On 07/04/2014 12:37 AM, Tom Davies wrote:

Hi :)
There are a few reasons;
*  Base needs an external back-end but most new users wont be aware of
that

Interesting. I never knew that Base "needs an external back-end"...
Perhaps you can get the documentation folks to add that to the help
files and the Base docs

This will be unlikely to happen in the short term as the so-called "split"
configuration is considered to be for experts only. The idea behind the
"embedded" configuration (i.e., a database back-end inside an ODF
container)
was developed to mask some of the database back-end detail and for
portability. While simpler, the embedded configuration is reported as
suffering greater data loss / corruption issues, due to the nature of the
packaging.

There are numerous threads over on the Apache OO forum about problems with
the embedded configuration. There is also a lengthy and detailed
discussion
about  Base / ODF container portability
<http://en.libreofficeforum.org/node/7876>   that provides several links
to
the mentioned Apache OO forum threads. Summary: In order for a "split"
configuration to become more widespread it would be ideal for some sort of
pack-n-go facility to be developed for Base to allow greater portability
of
data in a manner more in keeping with office documents.


I thought Base had HSQLDB built into it, but COULD use a different back
end if desired.  The only drawback I can see to using HSQLDB is that it
needs to be accessed from a Java environment.  I have used standalone
HSQLDB in Java apps and found it to be very robust and surprisingly fast in
light of the fact that Java is an interpreted language.

Dale Erwin


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-
unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.