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


Hi :)
Omg I go off on one sometimes!  It's not like I was really there or really
know or am in any position to judge anyone.  I didn't mean it to but my
post sounds very judgemental now I re-read it.  Sorry! :(

Wrt sniping and pulling in different directions working well sometimes - it
has worked really well for OpenOffice and LibreOffice.  Since we forked
there have been tons of articles and discussions about 'which is better' or
about alleged acrimony between us which has hugely helped "raise the
profile" of both.  Nowadays when I mention LibreOffice / OpenOffice to a
group of strangers there is usually at least 1, usually more, who uses one
of them!

Regards from
a Tom :)


On 27 May 2018 10:15, "Tom Davies" <tomcecf@gmail.com> wrote:

Hi :)
Access can be forced into using an external database and some people claim
it's easy but it makes a kludgy mess that makes it difficult and risky to
update Access.  It pushes people into buying other M$ database programs if
they need to upscale an Access database.  Access just is not designed to be
used that way.  Base is.

Java was widely advertised as being by far the best and sometimes as the
only way to write code that could be used on any machine using any OS.
Even today there are many expensive training courses teaching people how to
use it.  It's still kinda like "The Emporer's New Clothes".

Hsqldb is an excellent fast and light database program but it needs to be
kept updated, just like any program.  The version hard-coded into LO can't
be updated and is stuck on some ancient transitional version.  The
hard-coding was allegedly done by just 2 people without the support of the
Hsqldb community and against the wishes of LO's former, former, former
owners and community - however it did make it more competitive with
Access.  So it was a heroic effort and should have been supported and
applauded.

Future iterations of the in-built hsqldb(ish) were probably envisaged as
being closer to proper Hsqldb and as being made easier to update&upgrade -
but without the support of either community or their leadership the code
just stagnated for a few decades instead.  People sniping at each other and
pulling in opposing directions rather than helping and supporting each
other doesn't always work well.

The main reasons I really like the move to Firebird are;
1.  The name is more excitingly fashionable and easier to market
2.  Tactically good to have a refreshing break from our tragic past
regardless of whether it might have been easier and more consistent to just
upgrade to a newer, easier to upgrade, purer version of Hsqldb.  (Oddly it
would have been harder to go with Hsqldb and there discussions about which
way to go.)
3.  The move to C++ and away from Java - even though it's a step backwards
to a more geeky, less marketable name.

It is really great to see Base getting some much needed love and tlc.  It
deserves it.

Regards from
a Tom :)







On Sun, 27 May 2018 07:51 Robert Großkopf, <robert@familiegrosskopf.de>
wrote:

Hi *,

I 'm using the internal database for deveopement of databases, with
pupils in scool and for some little projects, which only need a
standalone-database. For "normal" use I also prefer MariaDB. The native
driver had some (little) problems here so I switched to JDBC. I am using

jdbc:mysql://«hostname»:3306/«databasename»?autoReconnect=true

to connect to MariaDB and don't loose the connection to the server.

Problem for MariaDB/MySQL: You have to know much about SQL or you must
create the tables with PHPMyAdmin or something else for using
Innodb-tables and create relationships between them.

Regards

Robert
--
Homepage: http://robert.familiegrosskopf.de
LibreOffice Community: http://robert.familiegrosskopf.de/map_3


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy


On Sun, 27 May 2018 07:51 Robert Großkopf, <robert@familiegrosskopf.de>
wrote:

Hi *,

I 'm using the internal database for deveopement of databases, with
pupils in scool and for some little projects, which only need a
standalone-database. For "normal" use I also prefer MariaDB. The native
driver had some (little) problems here so I switched to JDBC. I am using

jdbc:mysql://«hostname»:3306/«databasename»?autoReconnect=true

to connect to MariaDB and don't loose the connection to the server.

Problem for MariaDB/MySQL: You have to know much about SQL or you must
create the tables with PHPMyAdmin or something else for using
Innodb-tables and create relationships between them.

Regards

Robert
--
Homepage: http://robert.familiegrosskopf.de
LibreOffice Community: http://robert.familiegrosskopf.de/map_3


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy


-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

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.