Skip to content
← dbForge Studio for MySQL

I suggest you...

dbForge Studio for MySQL: Bugs

Categories

JUMP TO ANOTHER FORUM

(thinking…)

UI 'loses' SQL Security setting after schema compare

When we synchronise a DB schema with another we push the SQL SECURITY INVOKER setting but editing the destination/target procedure afterwards the GUI ignores this and reverts to DEFINER.

0 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Dazz Knowles shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Dazz Knowles commented  ·   ·  Report

    Hi,

    I've just retested this and it's now OK so I'd either accidentally set the "'Ignore DEFINER and SQL SECURITY clauses" option on or it's been fixed in the newer versions (I've been compiling a list for quite some time).

  • AdminDevart (_, Devart) commented  ·   ·  Report

    Could you please let us know whether the 'Ignore DEFINER and SQL SECURITY clauses' option is selected on the 'Options' page of the New Schema Comparison wizard? If so, this is the expected behavior of dbForge and you need to turn this option off.

    Otherwise, please provide us the full version of MySQL server and dbForge.