Hello Gusy...... Look keyword

rosyhyden — Tue, 03 Dec 2013 11:32:20 +0000

Hello Gusy......
Look keyword so some write content and click linking keyword so take more than more knowledge.....................

thanks for info

tejayasarapu — Tue, 26 Nov 2013 10:55:28 +0000

thanks for info

An SQL trigger cannot be

semaphore.v — Thu, 20 Jun 2013 06:23:26 +0000

An SQL trigger cannot be directly called from an application. An SQL trigger is invoked by the database management system on the execution of a triggering insert, update, or delete operation.

CREATE TRIGGER ai_SetURL

shivendra — Thu, 23 May 2013 05:22:13 +0000

CREATE TRIGGER ai_SetURL AFTER INSERT ON tblEvent
FOR EACH ROW UPDATE tblEvent SET EventURL=CONCAT("whatever.php?event=",EventID)

Triggers are used to perform

Tanmay — Thu, 23 May 2013 04:11:05 +0000

Triggers are used to perform particular action whenever some insert, update, delete commands executed, they are used to control, monitor and manage group of tables.

SELECT

teammatt3 — Fri, 06 Mar 2009 05:15:00 +0000

SELECT CONCAT("whatever.php?event=",EventID) AS EventURL FROM tblEvent

Building on pr0g's idea, you could create a view using that concat logic. Your client's editor probably wouldn't know the difference between a view and a table.

Another thing you might want to try is putting your update logic in a stored proc, and calling the stored proc in your trigger.

Shaggy wrote: You're

greg — Thu, 05 Mar 2009 20:51:00 +0000

Shaggy wrote:

You're trigger is fired 'on insert'
you're trigger is performing an update.

Logically yes, but seemingly you cannot update the same table that invoked the trigger, regardless of difference between query and trigger event type (possibly something to do with the MYSQL table lock- dunno).

It returns an error though, and there are bugs reported (and people venting their frustration) about this around the net, including on dev.mysql.com.

There are ways around certain requirements by using a BEFORE trigger.
But as trying to get next value of a MYSQL auto inc is a bad idea, Greg needs to do the actual insert first to obtain the auto increment ID to append to the 'VALUE' on UPDATE, using BEFORE wont work for him.

(also, obviously there would be no row to update to before the insert)

Link to an example

I'm still a little... not

Shaggy — Thu, 05 Mar 2009 19:00:30 +0000

I'm still a little... not sure of the emotion.. that MySQL doesn't support your trigger. I'm not buying the 'infinite loop' argument, no matter who's selling.

You're trigger is fired 'on insert'
you're trigger is performing an update.

You know, in a sane db that has sequences, you could just:

insert into test
(id,
val)
values
(nextval('sequence_name')
, 'url?id=' || currval('sequence_name'));

I know, you're all jealous of my MySQL free environment now, aren't you! -- this post provided no help to anyone... anywhere. It's been a long week.

Cheers,
Shaggy

Who said that? I changed my

greg — Thu, 05 Mar 2009 18:49:00 +0000

Who said that?

I changed my post (same time as you where writing) to give the reason why it's not what he wants.
But dammit you must have been pressing refresh until someone replied !

Wouldn't that need the row

pr0gr4mm3r — Thu, 05 Mar 2009 18:47:29 +0000

Wouldn't that need the row to have already been created (inserted) to obtain the ID.

Yes - insert the data normally, and then concat that extra bit of data when you select that row from the DB later.