"definer=" Missing In Trigger Definition

[hiero]

When you alter a trigger or perform a structure synchronization, the “DEFINER=” statement is missing. You can can only enter it manually before execution of the script.

This behavior causes problems when you work on a server from a remote machine as the DEFINER is set to something like 'root'@'192.168.0.43' if the DEFINER is not explicitly set. Depending on the setting of the server, this could prohibit the execution of trigger on the server if the definer isn't the typical DEFINER='root'@'localhost'.

[peterlaursen]

I think the problem is different MySQL versions!

When triggers were introduced in 5.o there was no 'definer' clause. It was added later.

Please tell the MySQL versions involved!

[hiero]

I'm using version 5.0.37 with a lot of triggers, functions and procedures.

[hiero]

And as I said in my first post, I can enter the 'definer' statement manually and it does what I want.

[peterlaursen]

Ok .. now I understand.

Agreed – we have inconsistences! With the 'definer' clause, as well as the 'SQL_SECURITY' clause.

For TRIGGERS the 'definer'clause is not shown (it is for VIEWs and SP's)

The 'SQL_SECURITY' clause is shown for VIEWs only .. not other objects.

When we introduced support for all those objects the two clasues were both not introduced in MySQL yet. The support that we added later is far from complete and sufficient. That is the history of it.

Actually I think in some situations it may cause problems to include those clauses and in some other situation it may cause problems NOT to include them .. so this should be an option ideally. We will need a little time to discuss the solution in details, but we will include improved dialogues/GUIs for exports, copy and structure sync in the 6.2 tree.

Thanks for reporting!

[peterlaursen]

Actually we have a pending request to provide an option NOT to include definer for VIEWs and SPs:

http://code.google.com/p/sqlyog/issues/detail?id=324

[Author]

Posts