dbexport bug
Posted in 1995
Topics: Stored Procedures & SPL, Server Administration, Security, Permissions & Auditing, Migration, Import/Export & Data Conversion
Hi all!
I noticed a fastidious bug in dbexport utility. If you place a comment
after the SP name, dbexport badly fails the generated sql script!!, so
you can't re-import it correctly.
For example, create this test database with a do-nothing procedure:
create database foo;
create procedure test_only { comment }
(p1 char(1), p2 smallint)
define p3 char(1); define p4 int;
let p3 = p1;
let p4 = p2;
end procedure;
and then export it. Dbexport schema (foo.sql) looks like this:
{ DATABASE foo delimiter | }
grant dba to "joe";
create procedure { comment }
"joe".test_only(1), p2 smallint) <<-- !!!!!!!!!!!!!!!!!
define p3 char(1);
define p4 int;
let p3 = p1;
let p4 = p2;
end procedure;
grant execute on "joe".test_only to "public" as "joe";
I tried up to 5.03 engine version. For curiosity, could anyone tell me
if bug still exists on most recent engines?
___*____
Ciao! | |_ e-mail
(_|oe |or <joefor@iperv.it>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--