Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of deeky666:
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:
Issue was closed with resolution "Fixed"