On Tue, Jun 9, 2020 at 11:05 AM Dan Lewis <[email protected]> wrote: > > Given this, what not update HSQLDB from 1.8 to 2.5?
IIRC there is a major architectural change to the HSQLDB code from 1.x to 2.x and the cost of making the code changes for an embedded mode (even the HSLQDB 1.8 is a customiazed release when used embedded in a Base file) would be very high. There is a secondary reason; to get away from an in-memory only DBMS (which HSQLDB still is) anda tertiary reason to get away from Java if possible, but of course that also means dumping the current Report Builder for some non-Java replacement. We were using this > version on the daily builds and later the alpha and beta version back in > 2005 and 2006. There has to be a way to convert from an embedded > database with version 1.8 to connecting to the database with JDBC with > version 2.5 that is not really difficult. The main problem is with > moving the queries, forms, and reports. > > Dan > > On 6/9/20 07:45, Alexander Thurgood wrote: > > Le 09/06/2020 à 06:28, Pulkit Krishna a écrit : > > > > Hi Pulkit, > > > > Yes, this change was made in master and also pushed into the 6.4.4 > > branch - it was deliberate. > > > > The reason is that the embedded Firebird support code just too much of a > > liability at the moment, and virtually no one is fixing the bugs that > > its introduction has created, or the bugs for features that one would > > expect to see in such an engine, but which haven't been implemented in > > the LO code. It was a whole sorry mess, just waiting to explode in the > > faces of unwitting users, so it was felt better to switch it back to > > experimental, that way, if people hose their data with it, they will > > have made the decision knowingly, rather than by default building their > > hopes up and then kicking them where it hurts. > > > > At least with embedded hsqldb 1.8.0, we know where all of the problems > > lie, and the documentation doesn't need to be rewritten for a new db > > engine that doesn't deliver on the promises our marketing communication > > was so keen to tout (the engine itself is actually pretty capable, its > > just the implementation within LO that is somewhat lacking). > > > > > > Alex > > > > > > -- > To unsubscribe e-mail to: [email protected] > 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/documentation/ > Privacy Policy: https://www.documentfoundation.org/privacy -- To unsubscribe e-mail to: [email protected] 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/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
