So, what appears to be happening is consensus that other database
back-ends should be used.
What is implied, is that Base does not have the ability to generate from a
package, the selected external database of choice.
1. Is this correct?
2. Should it be corrected?
3. When generated, should 'internal' mean in the same folder, 'external'
mean somewhere else?
On 8/4/2014 10:36 AM, Wolfgang Keller wrote:
Average end-user is challenged enough just installing an O/S and
productivity suite, and learning how to use them, much less a real
PostgreSQL is pretty foolproof to install and use. I know what I am
talking about since I am the reference fool.
It may be something different if you need to maintain it for running a
huge database that gets a serious load of queries and transactions and
needs to be fault-tolerant, accessible from the "public" Internet etc.
But for "home" or "small business" use cases it's really simple.
Plus: MS Office (Pro) has one, so LibréOffice and relatives
have to have one.
Access is a dangerous heap of junk.
I know of Access users who get their database corrupted roughly every
four weeks on average.
Yes: Such tools should never, ever be used for anything very
Base looks and feels like a perfectly credible "CRUD" and
reporting frontend for a database. It's just the choice of an embedded
database for storage that's a mistery for me.
At best, it's useless to include HSQL. At worst, it might discredit LO
as a whole.
To unsubscribe e-mail to: firstname.lastname@example.org
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
Impressum (Legal Info)
: 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