You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
When a schema name is used as a qualifier on a table in an insert statement, the
last column of the column list is reported as a table from
get_routine_dependencies.
This is the result of the sample procedure below.
+-------------+-------------+-------------+--------+
| schema_name | object_name | object_type | action |
+-------------+-------------+-------------+--------+
| myschema | col2 | table | insert |
| myschema | sometable | table | insert |
+-------------+-------------+-------------+--------+
If you omit the schema name, the result would be this instead:
insert into sometable (col1, col2)
values (var1, var2);
+-------------+-------------+-------------+--------+
| schema_name | object_name | object_type | action |
+-------------+-------------+-------------+--------+
| myschema | sometable | table | insert |
+-------------+-------------+-------------+--------+
Can you provide with sample data?
create procedure testproc()
begin
insert into myschema.sometable (col1, col2)
values (var1, 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 4:10
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 31 Oct 2014 at 4:10The text was updated successfully, but these errors were encountered: