Re: About putting back Firebird experimental

2019-09-04 Thread Terrence Enger
On Wed, 2019-09-04 at 16:59 +0200, Alexander Thurgood wrote: > > I feel we would do well to remember that this is people's live and > valuable data we are potentially messing with here, and not all of these > users are DBAs, in fact rather the contrary. It matters not a jot that > db engine XYZ

Re: About putting back Firebird experimental

2019-09-04 Thread julien2412
Xisco Fauli wrote > if we want to put it back to experimental, personally I would prefer to > do it *only* in 6.3 and leave it as it's in master so we can test it and > improve it. > ... It can be tested on master sources just by enabling experimental. We already put in release notes for 6.3 that

Re: About putting back Firebird experimental

2019-09-04 Thread Alexander Thurgood
Le 22/08/2019 à 12:12, Jean-Pierre Ledure a écrit : Hi all, > (3) the limits are different: e.g. VARCHAR max. length is < 2Gb in > Hsqldb and  < 32K in Firebird, the max. length of a table row is < 2Gb > in Firebird and <64K in Firebird, the max. length of a column name is > 128B in Hsqldb and

Re: About putting back Firebird experimental

2019-09-04 Thread Xisco Fauli
Hi Julien, if we want to put it back to experimental, personally I would prefer to do it *only* in 6.3 and leave it as it's in master so we can test it and improve it. In the past, We did the same in 6.2 <

Re: About putting back Firebird experimental

2019-08-29 Thread julien2412
For information, I pushed the patch https://gerrit.libreoffice.org/#/c/78240/ If someone sees some regressions or wants to comment, don't hesitate to tell of course so we can push an additional patch or revert this one if it brings too much regression/confusion. -- Sent from:

Re: About putting back Firebird experimental

2019-08-27 Thread Julien
Hi Caolán, Considering all the feedback, I submited https://bugs.documentfoundation.org/show_bug.cgi?id=127180 about putting Migration + propose by default Firebird in experimental. To fullfil this, reverting

Re: About putting back Firebird experimental

2019-08-22 Thread Lionel Élie Mamane
I note that the tracker bug https://bugs.documentfoundation.org/show_bug.cgi?id=51780 which is supposed to list bugs we want to see fixed _before_ switching to Firebird by default for new files has approx 35 blockers. Note that these bugs are not (supposed to) include any bugs about migration,

Re: About putting back Firebird experimental

2019-08-22 Thread Jean-Pierre Ledure
Hi, the migration of a (single-user) database from one RDBMS to another copes with 3 main families of issues: (1) the SQLs are not compatible: each has its own dialect, the list of builtin functions is different, etc. This is visible each time "Direct SQL" is used in LO, i.e. when making a

Re: About putting back Firebird experimental

2019-08-22 Thread Caolán McNamara
On Tue, 2019-08-20 at 14:51 +0200, Alexander Thurgood wrote: > Le 20/08/2019 à 10:28, Julien a écrit : > > Hi Julien, > > +1 from me. > > As a QA triager, I can but agree with Julien given the current stage > of development. The migration code still fails to handle multiple, > basic elements of

Re: About putting back Firebird experimental

2019-08-20 Thread Robert Großkopf
Hi Julien, migration wizard is a good help for people, who know how to fix the other issues, which would appear. I have migrated some databeses from the Base-Handbook to Firebird. I know I first have to save the old file. So I open the fiel in 6.3.0.4 with a backup and let the migration wizard

Re: About putting back Firebird experimental

2019-08-20 Thread Alexander Thurgood
Le 20/08/2019 à 10:28, Julien a écrit : Hi Julien, +1 from me. As a QA triager, I can but agree with Julien given the current stage of development. The migration code still fails to handle multiple, basic elements of embedded hsqldb ODB files found in actual use. If it can't even do the basics

About putting back Firebird experimental

2019-08-20 Thread Julien
Hello, Considering the number of bugs about Firebird migration (see https://bugs.documentfoundation.org/show_bug.cgi?id=116968) and the fact that these bugs may not be trivial to fix (see https://wastack.wordpress.com/2018/07/25/database-migration-in-libreoffice-bug-fixes-and-more/), thought