Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
GoogleCodeExporter opened this issue Jun 18, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

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 [email protected] on 31 Oct 2014 at 3:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant