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


 Grivin,

Thanks, no doubt you're correct as I admittedly did not research adoption of
HSQLDB  further.  And that predates my use of OpenOffice. Was fighting with
Sybase and Oracle products, while avoiding MS Access.

Interesting history none the less :-)

Stuart


Girvin R. Herr wrote
To keep the record straight, Stardivision's StarOffice did not use 
HSQLDB.  Unless the name has been changed, Stardivision used the ADABASE 
D database engine in their StarOffice.  As far as I can research, Sun 
dropped the proprietary Adabase D engine in favor of HSQLDB after it 
took over the StarOffice code from Stardivision.  I never was able to 
get Adabase D working for me back then, but I was ignorant of real 
(non-Access) databases then and the StarOffice Adabase D database 
documentation was terrible.
Girvin Herr





--
View this message in context: 
http://nabble.documentfoundation.org/HSLQLDB-syntax-tp4065310p4065574.html
Sent from the Users mailing list archive at Nabble.com.

-- 
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.