gunarajesh / common-schema

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

Routine dependencies confused by <insert ... on duplicate update> #69

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 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?
An insert statement with <on duplicate key update>
will make the get_routine_dependencies procedure think
there is an update to a table with the 
name given by the column name.
The procedure should not report col2 below since this is a column.

+-------------+-------------+-------------+--------+
| schema_name | object_name | object_type | action |
+-------------+-------------+-------------+--------+
| myschema    | col2        | table       | update |
| myschema    | mytable     | table       | insert |
+-------------+-------------+-------------+--------+

Can you provide with sample data?
create procedure testproc(
  var1 int,
  var2 int
)
begin
  insert into mytable (col1, col2)
  values (var1, var2)
  on duplicate key update
    col2 = var2;
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 3:50

GoogleCodeExporter commented 8 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