Hi Frederic-Emmanuel,

On Tue, 3 Jan 2017 15:02:08 +0000 PICCA Frederic-Emmanuel
<frederic-emmanuel.pi...@synchrotron-soleil.fr> wrote:
> 1) On Jessie 
> 
> with the tango account
> 
> mysql> use tango;
> mysql> show create procedure class_att_prop\G
> 
> I got  "Create Procedure": NULL
> 
> But If I use the root account (mysqladmin)
> 
> CREATE DEFINER=`root`@`localhost` PROCEDURE `class_att_prop` (IN class_name 
> VARCHAR(255), INOUT res_str BLOB)
> 
> which shows clearly that on jessie the procédure where created with the admin 
> account
> 
> 2) On stretch
> 
> with the tango account
> 
> > CREATE DEFINER=`tango`@`localhost` PROCEDURE `class_att_prop` (IN 
> > class_name VARCHAR(255), INOUT res_str MEDIUMBLOB)
> 
> Which shows that the procedures were created with the right tango account.
> 
> Now the question is how can we fix this ?

I am not sure that I follow what you are doing, but if you need the code
to be run with the dbadmin privileges, you should put the code in:
    /usr/share/dbconfig-common/data/PACKAGE/upgrade-dbadmin/DBTYPE/VERSION
instead of in:
    /usr/share/dbconfig-common/data/PACKAGE/upgrade/DBTYPE/VERSION

Please consult the documentation here:
https://www.debian.org/doc/manuals/dbconfig-common/ch-develguide.html#s-updates
and (describing the difference):
https://www.debian.org/doc/manuals/dbconfig-common/ch-develguide.html#s-bootstrap

Paul

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to