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 derived from it.
thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:
We use Jira to track the state of pull requests and the versions they got
See the documentation for reference on that.
@deeky666 any reason for it to be ' ' and not ''? I don't really get it
@Ocramius yeah you are right. Adopted it from SQLServerPlatform. Seems ORM is always prepending a space anyways. I'll change that, thanks.
fix FOR UPDATE SQL on SQL Anywhere