Mysql on duplicate key condition (IF) setting of one field

For mysql your syntax is very off

see manual

it mus be

insert into data_manager.rars_CoachTypes 
  
(coach_type,template_height,template_width,seat_height,seat_width,toc,templateURL,serviceId,latest_depart_date,our_template_width,our_template_height,features,imported) values (1,1,1,1,1,1,1,1,1,1) 
  on duplicate key update
    template_height=VALUES(template_height),
    template_width=VALUES(template_width),
    seat_height=VALUES(seat_height),
    seat_width=VALUES(seat_width),
    templateURL=VALUES(templateURL),
    latest_depart_date=VALUES(latest_depart_date),
    updated = IF (templateURL<>VALUES(templateURL),1,0);

or as Barmar correctly said, you can use use OLD and NEW to differentiate both values

insert into data_manager.rars_CoachTypes 
  
(coach_type,template_height,template_width,seat_height,seat_width,toc,templateURL,serviceId,latest_depart_date,our_template_width,our_template_height,features,imported) values (1,1,1,1,1,1,1,1,1,1) as NEW
  on duplicate key update
    template_height=NEW.template_height,
    template_width=NEW.template_width,
    seat_height=NEW.seat_height,
    seat_width=NEW.seat_width,
    templateURL=NEW.templateURL,
    latest_depart_date=NEW.latest_depart_date,
    updated = IF (templateURL<> NEW.templateURL,1,0)

Sorry for the confusion over the IF syntax. My real SQL is somewhat more complex and I had removed some to make it simpler for this post and accidentally removed the TRUE/FALSE parameters as well... That was not the problem.

It turns out that the ALIAS is the problem. If I add an alias I get the error. Remove it and the error goes away. Not sure why an alias is not permitted here...?

My SQL now looks like this and works:

insert into data_manager.rars_CoachTypes
  (coach_type,template_height,template_width,seat_height,seat_width,toc,templateURL,serviceId,latest_depart_date,our_template_width,our_template_height,features,imported) values ? as NEW
  on duplicate key update
    updated = IF(OLD.templateURL <> NEW.templateURL,1,0),
    template_height=NEW.template_height,
    template_width=NEW.template_width,
    seat_height=NEW.seat_height,
    seat_width=NEW.seat_width,
    templateURL=NEW.templateURL,
    latest_depart_date=NEW.latest_depart_date

Thanks to @ysth for pointing out that the order is important for ensuring "updated" get sets correctly and for suggesting I reference the table directly instead of using an alias which ultimately was coirrect way to remove the error.

Order matters; you must set updated before setting templateURL, or your expression will compare the new value to the value to be set (resulting in updated always being 0). This was true using the VALUES() function and remains true using the VALUES alias.

fiddle

In general, when you use a column value in an expression in an update, it has the value as of the time it gets to that expression. Multitable updates work a little differently, though not in a way that makes any sense.

Your if syntax was incorrect; you were missing 2 parameters:

IF (c.templateURL<>INSERTDATA.templateURL,1,0)

with those, either IF or your CASE will work (with updated= moved before templateURL=). When you get a "You have an error in your SQL" error, look closely at where it said the error occurs (and what immediately precedes that ). That could have clued you in to the bad IF syntax.

About aliases, on the left side of the column update =, an identifier can only refer to one of the tables being updated, so templateURL= is unambiguous, but on the right, templateURL could refer to either rars_CoachTypes or INSERTDATA, so needs to be qualfied. You should explicitly say data_manager.rars_CoachTypes.templateURL.