[jonb2]

PS.

A. I have just checked Heidi, it does what I want. It saves the edit.

'ashwin' wrote:

@jonb2.. We checked with HeidiSQL. Yes, they do allow to edit and save trigger. But..on SAVE they execute these queries(Checked from their query LOG)-

Code:

DROP TRIGGER `customer_create_date`;
/* 0 rows affected. */
CREATE DEFINER=`root`@`localhost` TRIGGER `customer_create_date` BEFORE INSERT ON `customer` FOR EACH ROW SET NEW.create_date = NOW();

Now, with SQLyog when you do Execute All these queries are executed-

Code:

DROP TRIGGER /*!50032 IF EXISTS */ `customer_create_date`;
CREATE ;

Priority fix, of course!

[jonb2]

P. I *think* you have missed my point 🙂

Take the trigger below. I want to edit it, not run it. How do I edit and save it – easily? At the moment it wants to save it as SQL if I want to save it.

Secondly, take a look at it and to illustrate. I do not need the title of the trigger copied on a double-click, as it is already created, it already exists, it is not a dead parrot.

I think triggers need their own edit box perhaps.

==============================

DELIMITER $$

USE `iwin`$$

DROP TRIGGER /*!50032 IF EXISTS */ `links_ins`$$

CREATE

TRIGGER `customer_create_date` BEFORE INSERT ON `customer` FOR EACH ROW SET NEW.create_date = NOW() ;

So both HeidiSQL and SQLyog does the same. But they have this SAVE and we have Execute All.

If I do not understand your concern it would be better if we have GoToMeeting session. Please tell us in which timezone you are in and suitable time to have online screen sharing session using GoToMeeting?

You can create a ticket for privacy(By mailing us to [email protected]).

[jonb2]

Hi Peter

Yes, I can see your point. Conceded. But in this case it's recursive. You cannot re-use the trigger name in the edit once it's been created. I can live with it.

I just bought the ultimate version yesterday and was playing with it (missed the voucher which appeared in my inbox this morning, c'est la vie!).

I have another issue. I cannot see an easy way of altering a trigger and saving it without doing an SQL dump. Is there a way? As this seems particularly laborious. If not, I would ask this added to the feature list ASAP 🙂

Kind regards

Jon

'peterlaursen' wrote:

It is not a bug. It is per design.

The name of any database object (database, table, column, index trigger .. whatever) will be pasted to the current open edditor window on doubleclick. You can turn off this from tools .. preferences .. 'general' tab .. uncheck 'paste object name in editor on doubleclick'.

What did you expect would happen when doubleclicking on the trigger name?

[jonb2]

Hi Peter

Good grief, what service 🙂

Checking it – it seems it happens when there is no data in the column.

The server is 5.5.8.

Not your problem then … but a MySQL thing.

Kind regards

Jon

[Author]

Posts