Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-17 Thread PICCA Frederic-Emmanuel
> Ehm, yes. :) so I just tested an upgrade from jessie to sid of tango-db and it works :))) Now I have only one concern about the dump. Since we had a failure with the dump when it ran as user, we discovered that our procedures where wrong and necessitate the dbadmin grants in order to works.

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-16 Thread Paul Gevers
Hi Frederic-Emmanuel, On 01/16/17 18:10, PICCA Frederic-Emmanuel wrote: >> Officially, no, because the documentation says: "If files exist in both >> data and scripts, they will both be executed in an unspecified order." >> However, the current behavior of dbconfig-common is to first run the >>

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-16 Thread PICCA Frederic-Emmanuel
Hello Paul > Officially, no, because the documentation says: "If files exist in both > data and scripts, they will both be executed in an unspecified order." > However, the current behavior of dbconfig-common is to first run the > script and then run the admin code and then run the user code. So

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-15 Thread Paul Gevers
Hi Picca, On 01/14/17 11:12, PICCA Frederic-Emmanuel wrote: > Hello Paul > >> I really hope I can upload this weekend. I have code that I believe does >> what I want. I am in the process of testing it. > > thanks a lot. I'll upload in the next hour. >> What I meant, >> instead of the mysql

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-14 Thread PICCA Frederic-Emmanuel
Hello Paul > I really hope I can upload this weekend. I have code that I believe does > what I want. I am in the process of testing it. thanks a lot. > [...] > What I meant, > instead of the mysql code that runs as user, run a script for the > upgrade (they are run with database

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-13 Thread Paul Gevers
Control: tags 850190 pending Hi Frederic-Emmanuel, On 01/13/17 16:08, PICCA Frederic-Emmanuel wrote: >> Once I fixed 850190, > > Do you think that you will fix this bug before next week in order to > let me enought time to fix tango and upload it. I really hope I can upload this weekend. I

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-13 Thread PICCA Frederic-Emmanuel
Hello Paul, > Once I fixed 850190, Do you think that you will fix this bug before next week in order to let me enought time to fix tango and upload it. > I believe that ought to work, although that is > still a hack. I was thinking of doing the "DROP PROCEDURE IF EXISTS *" > calls with the

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-08 Thread Paul Gevers
Hi Frederic, On 05-01-17 18:21, PICCA Frederic-Emmanuel wrote: > It is true that for now my package works only if the database name is tango. > > this is a limitation but I do not want to mix this into this bug report. Ack. > so can you help me write the right snipser at the right place in the

Bug#848137: [Dbconfig-common-devel] Bug#848137: problem with the upgrade of tango-db

2017-01-05 Thread PICCA Frederic-Emmanuel
Hello, I discuss with the tango-db upstream and he found that this one line fixed the problem, befrore doing the tango-db upgrade UPDATE mysql.proc SET Definer='tango@localhost' where Db='tango'; Ideally it should be something like UPDATE mysql.proc SET Definer='xxx' where Db='yyy'; where