Merge lp:~stub/launchpad/pending-db-changes into lp:launchpad/db-devel
Proposed by
Stuart Bishop
on 2010-12-15
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Stuart Bishop on 2010-12-15 | ||||
| Approved revision: | no longer in the source branch. | ||||
| Merged at revision: | 10059 | ||||
| Proposed branch: | lp:~stub/launchpad/pending-db-changes | ||||
| Merge into: | lp:launchpad/db-devel | ||||
| Diff against target: |
54 lines (+10/-22) 1 file modified
database/schema/upgrade.py (+10/-22) |
||||
| To merge this branch: | bzr merge lp:~stub/launchpad/pending-db-changes | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Jelmer Vernooij (community) | code | 2010-12-15 | Approve on 2010-12-15 |
|
Review via email:
|
|||
Commit Message
[r=jelmer]
Description of the Change
Per Bug #689642, database patches could be applied locally if they did not terminate with a semicolon, but would fail when applied to a replicated environment. This bug would also apply to trusted.sql and comments.sql.
I fixed this by removing some unnecessary code where we were splitting the patches into statements and failing if we attempt to apply an sql script with no terminating semicolon.
To post a comment you must log in.

As discussed on IRC, please clarify the error message to mention that the last non-whitespace character in the file should be a semicolon - in case the last line contains a comment.