dream120 / common-schema

Automatically exported from code.google.com/p/common-schema
0 stars 0 forks source link

Routine dependencies confuses default schema #67

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Which version of common_schema are you using? (specify
revision+distribution)
2.2.11
revision 523

Which component is failing? (specify the view, function, etc.)
get_routine_dependencies

What is the expected output? What do you see instead?
A statement that uses a table without a schema qualifier is given
the wrong schema name in the routine dependencies output.
The sample procedure is in schematwo schema and since table2 has no qualifier 
it should be expected to exist in the same schema.

The get_routine_dependencies reports schemaone.table2 instead of 
schematwo.table2.

Can you provide with sample data?
create procedure schematwo.testproc()
begin
    select *
    from schemaone.table1 t1
    join table2 t2
      on t2.someid = t1.someid;
end //

(As of version 1.1), please provide output of
SELECT * FROM common_schema.status

                       project_name: common_schema
                            version: 2.2
                           revision: 523
                       install_time: 2014-10-31 08:31:35
                    install_success: 1
          base_components_installed: 1
 innodb_plugin_components_installed: 1
percona_server_components_installed: 0
              install_mysql_version: 5.6.17
                   install_sql_mode: NO_AUTO_VALUE_ON_ZERO,NO_ENGINE_SUBSTITUTION

Please provide any additional information below.

Original issue reported on code.google.com by lars.gra...@gmail.com on 31 Oct 2014 at 2:10

GoogleCodeExporter commented 9 years ago
Thank you -- routine dependencies are still in BETA, and are not being actively 
pursued. I don't expect this to be fixed (unless someone contributes a patch)

Original comment by shlomi.n...@gmail.com on 13 Dec 2014 at 7:22