lp:~stub/lazr-postgresql/devel

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:lazr-postgresql at revision 15

j.c.sackett (community): Approve on 2012-05-03

Diff: 684 lines (+355/-41)

15 files modified

.bzrignore (+1/-1)
.testr.conf (+1/-1)
NEWS (+4/-2)
README (+6/-6)
buildout.cfg (+1/-1)
ez_setup.py (+284/-0)
setup.py (+13/-7)
src/lazr/__init__.py (+22/-0)
src/lazr/postgresql/__init__.py (+2/-2)
src/lazr/postgresql/migrate.py (+3/-3)
src/lazr/postgresql/tests/__init__.py (+2/-2)
src/lazr/postgresql/tests/test_migrate.py (+3/-3)
src/lazr/postgresql/tests/test_upgrade.py (+6/-6)
src/lazr/postgresql/upgrade.py (+5/-5)
versions.cfg (+2/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

19. By Stuart Bishop on 2012-10-15

Access columns by name

18. By Stuart Bishop on 2012-05-23

Not a byte string

17. By Stuart Bishop on 2012-05-23

open, not file

16. By Stuart Bishop on 2012-05-08

Pull in and update some helpers from Launchpad

15. By Stuart Bishop on 2012-05-08

Move to lazr.postgresql namespace

14. By Robert Collins on 2011-12-12

Make it possible to dump the SQL that was executed (fugly but good for debugging).

13. By Robert Collins on 2011-12-12

Do not attempt to dry-run apply CONCURRENT patches. (They cannot be dry-run applied.

12. By Robert Collins on 2011-12-12

Add a one-only option for production rollouts - rollout the next patch and only that.

11. By Robert Collins on 2011-12-11

CLI entry point working.

10. By Robert Collins on 2011-12-11

Allow applying all patches regardless of type in one invocation.