Am 28.07.2011 00:47, Tom Cloyd wrote:
An obvious alternative, as well: move data tables to a non-java db, and
use LO as front end for that - sqlite might be a reasonable first choice.
t.
Yes, MySQL, SQLite, PostrgreSQL can circumvent your Linux/Java problem 
while providing first class database engines. I run a HSQLDB server 
because the databases transformed seamlessly from embedded HSQLDB drafts 
and the performance problem does not occur on Windows systems where the 
databases are in productive use.
H2 was an experiment when the performance issue was not apparent. H2 is 
a great database engine, very easy to set up for exclusive use on the 
local machine (drop files and use URL).
I expect Base to fall apart, and it will be a big relief as long as the 
mere database connectivity and form controls persist. If not, I can not 
use this office suite anymore since all our spreadsheet models and most 
of the Writer templates are connected to some database one way or the other.
On 07/27/2011 04:19 PM, Tom Cloyd wrote:
Thanks, Andreas.
You're welcome,
--
Unsubscribe instructions: E-mail to users+help@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.