gourmet team mailing list archive
-
gourmet team
-
Mailing list archive
-
Message #00003
Database changed without update code???
Bernhard et al,
I've been a bit busy and haven't followed all the development leading up to
the 0.16 release, but it looks like 0.16.0 went out with changes to the
database model but *without* code to update existing databases.
Specifically, it seems like primary keys have been changed in the pantry
and other columns.
This is pretty bad -- I've always tried to ensure that existing users get
treated well. I'm wondering, have bug reports been flowing in about this?
Is 0.16 not out generally?
For the future, changes to the DB structure are a pain in the ass and
shouldn't be made for simple "code cleanup" reasons -- I doubt there is any
functional benefit to introducing new primary key columns named 'id' in
place of or in addition to the old ones? I would tend to be inclined to
just roll back the changes (that's what I'll do locally), but since the
code is now in the wild and new users will get the new columns, I think we
have to write the update code anyway.
Tom
Follow ups