DBAL-856: [GH-561] Fix FOR UPDATE SQL on SQL Anywhere #2093

doctrinebot opened this Issue Mar 31, 2014 · 3 comments

2 participants


Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of deeky666:

Url: #561


It looks like there was a misunderstanding on SQL Anywhere with the FOR UPDATE SQL as this is actually a statement used in prepared statements and does not work the ANSI way in ORM. So I removed it in favour of the table lock hint implementation which works out quite well and makes the getForUpdateSQL() rather useless anyways. SQL Server does it like this, too btw and both dialects are pretty similar because SQL Anywhere once drived from it.


Comment created by @doctrinebot:

A related Github Pull-Request [GH-561] was closed:


Comment created by @ocramius:

Merged: 6a120fb


Issue was closed with resolution "Fixed"

@doctrinebot doctrinebot added the Bug label Dec 7, 2015
@Ocramius Ocramius was assigned by doctrinebot Dec 7, 2015
@doctrinebot doctrinebot added this to the 2.5 milestone Dec 7, 2015
@doctrinebot doctrinebot closed this Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment