[DBAL-389] [GH-232] Problem with sequence names, PostgreSQL and MixedCased schemas Created: 22/Nov/12 Updated: 22/Nov/12 Resolved: 22/Nov/12 |
|
| Status: | Resolved |
| Project: | Doctrine DBAL |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Security Level: | All |
| Type: | Bug | Priority: | Major |
| Reporter: | Benjamin Eberlei | Assignee: | Benjamin Eberlei |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
This issue is created automatically through a Github pull request on behalf of ajgarlag: Url: https://github.com/doctrine/dbal/pull/232 Message: I''m having problems with a doctrine migration in a pgsql database that has a mixed case schema name. After some investigation I've found the origin of the problem: when the schema manager is going to list sequences it executes a SQL statement to find the minimun sequence value. This SQL statement is not quoting the sequence name, so the SQL fails with mixed cased schemas. This trivial commit resolves this problem. I think it could be backported to stable versions of DBAL. |
| Comments |
| Comment by Benjamin Eberlei [ 22/Nov/12 ] |
|
A related Github Pull-Request [GH-232] was closed |