Details
Bug
Resolved
Major
Description
Whenever DBAL Schema Manager tries to rename a table in sql server 2008 it should use also the sp_RENAME procedure. Otherwise error is thrown.
Apparently a similar issue was fixed for column ALTER Commands as described in the link below, but also the ALTER TABLE command should use sp_RENAME to avoid crash.
Suggested fix for Latest DBAL 2.2
From Line 283:
$queryParts[] = 'RENAME TO ' . $diff->newName;
To Line 283:
$sql[] = 'sp_RENAME \'' . $diff->name . '\',\'' . $diff->newName.'\'';
This seems to fix the problem.
Hope this helps
Sorry for my bad english.
Fredcallagan
Activity
Benjamin Eberlei
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Workflow | jira [ 13627 ] | jira-feedback2 [ 17605 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 17605 ] | jira-feedback3 [ 19958 ] |
Benjamin Eberlei
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 2.2.3 [ 10210 ] | |
| Resolution | Fixed [ 1 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DBAL-254, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
Fixed.