Repository navigation
[upgrade 0.13.8->0.15.x] TypeError: an integer is required #678
Description
This is related to previous Metakit -> SQLite -> SQLAlchemy upgrades that didn't convert (at least) some "pickled" booleans and that's biting many users now, see e.g.
- https://bugzilla.redhat.com/show_bug.cgi?id=659994 (for Gourmet 0.15.6)
- https://sourceforge.net/projects/grecipe-manager/forums/forum/371768/topic/4863028
- https://bugs.launchpad.net/gourmet/+bug/1010659 (probably related, though maybe not correctly diagnosed by the bug reporter)
The above reports (and attached recipe databases) seem to indicate that the "pickled" values were introduced by Metakit, did work okay with SQLite but are now causing problems for SQLAlchemy.
Normally, this error looks about like
sqlite:////home/user/.gourmet/recipes.db
TRYING TO GET ingkey pantry from pantry
ERROR!!!
Traceback (most recent call last):
File "/usr/share/gourmet/gourmet/backends/db.py", line 2027, in items
val = getattr(i,self.vp)
TypeError: an integer is required
IGNORING
[...]
sqlalchemy.exc.IntegrityError: (IntegrityError) column ingkey is not unique u'INSERT INTO pantry (ingkey, pantry) VALUES (?, ?)' ((u'oil, olive', 1), (u'black pepper, ground', 1), (u'flour, all purpose', 1), (u'ice', 1), (u'sugar', 1), (u'water', 1), (u'oil, vegetable', 1), (u'salt', 1))
Activity
ockham commentedon Feb 1, 2013
The obvious culprit is the
pantrycolumn in thepantrytable (which holds pickled Booleans), as examining two of the recipes.db files from the downstream bug trackers reveals. Fixing this is quite straight-forward and almost done.There's however also the
shopcategorycolumn in theshopcatstable which holds pickled strings, and that's a bit more complicated to fix.Close Launchpad bug #1010659 (== our issue #678).