sloecode-dev team mailing list archive

[Thomi Richards <thomir@xxxxxxxxx>]

Ladies & Gentlemen,


I have just merged in my database migration changes, and pushed to
launchpad. The involve rather large changes in both lp:sloecode and
the debian branch. Briefly, the changes include:

 1) Database config is now stored in a separate .ini file
(database.ini). In development mode (i.e.- running using 'make' or
'paster') this file is read and used to initiate sqlalchemy. In
production mode, the database.ini file is generated by dbconfig-common
in /etc/sloecode/

2) Database schema is now created as part of the install process
(again, by dbconfig-common). This is a big improvement, because it
means you can go from nothing to a fully working sloecode install with
one line: "apt-get install sloecode" - that's it. No config file
editing, no messing around.

3) The database schema is installed in the 'dbpatches' folder. We
support mysql and sqlite. These schema changes MUST NOT CHANGE. Is
there a way to lock them in Bazaar maybe? Anyway, if we want to patch
the schema, we need to write patch files that upgrade to the next
version (one for each back-end). I plan to cross this bridge when we
get there, but it's not going to be a problem.

So, you may find that things stop working after you upgrade! The first
thing to check is the database.ini file - if the default settings are
wrong then you'll need to tweak them.

I'd like some feedback from anyone using the PPA packages!


Cheers,