The idea behind "DELAY" is to allow queries that don't need to commit immediately to just kinda happen when they get there. However, it is not part of standard SQL. It doesn't work on PostgreSQL or SQLite. It only works on MySQL. However, it only works on the MyISAM table type. Drupal 7 on MySQL now defaults to InnoDB, where DELAY is ignored. So really, it's an edge case that we don't even use.

Should we just get rid of it and save ourselves the hassle?

CommentFileSizeAuthor
#5 kill-delay.patch2.37 KBjbrown
#1 772554-delay.patch2.52 KBCrell
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Crell’s picture

Status: Active » Needs review
FileSize
2.52 KB

I couldn't find anywhere that we were using delay() in the first place.

chx’s picture

Status: Needs review » Reviewed & tested by the community

Totally. DELAYED means "the day when my database melts down has been delayed by an undefined amount of time". Using INSERT DELAYED adds a lot of interesting problems and altogether you might end up with a lower INSERT performance. More importantly you give up control on what happens with your database. Bad idea.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

Yay for less code! :) Committed to HEAD.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jbrown’s picture

Status: Closed (fixed) » Needs review
FileSize
2.37 KB

There is more code to be removed.

I also removed the docs: http://drupal.org/node/310079/revisions/view/773668/1024872

aspilicious’s picture

Looks good

Crell’s picture

Status: Needs review » Reviewed & tested by the community

Dagnabbit, I thought I got some of those. Thanks, jbrown.

Dries’s picture

Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD. Thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.