import problem "column ingkey is not unique"

  • m0par70

    m0par70 - 2006-10-07

    First of all, thanks for the prog. Very useful.

    I upgraded to 0.12.0.pre1 and get

    Traceback (most recent call last):
      File "/usr/share/gourmet/", line 440, in init_recipes
      File "/usr/share/gourmet/", line 64, in check_for_data_to_import
      File "/usr/share/gourmet/", line 230, in import_backup_file
      File "/usr/share/gourmet/backends/", line 314, in do_add
      File "/usr/share/gourmet/backends/", line 73, in execute
    IntegrityError: column ingkey is not unique

    It appears as though I ended up with duplicate ingredient entries under the old gourmet. Is there any hope, or do I need to reenter all the old recipes?


    • m0par70

      m0par70 - 2006-10-07

      After playing with it for a while, I seem to have recovered.

      I looked in .gourmet and found that I had both and recipes.db. Scanning recipes.db, I found no recipe information, just ingredient info. So I deleted recipes.db and restarted gourmet. Import went fine.

      I had an issue with debian's metakit (no proper packages available for sid), so when I started the upgraded gourmet the first time without metakit the .db file must have been created. After compiling and installing custom metakit packages, the new gourmet seemed to have become a little confused when both recipe.db and .mk files are available.

      All is well...

    • tom

      tom - 2006-10-07

      This is a bug. -- Please submit a bug report and, if you can, attach a copy of your .mk file (or e-mail it to me if you don't want to make it public) so I can figure out what's going on.

      • m0par70

        m0par70 - 2006-10-07

        Sorry if I'm just stupid, but looking at the posting times, I wonder if you saw my follow-up reply.

        Do you still think it is a bug, or was it just due to my starting without metakit the first time, then restarting with metakit installed?

        If you still think it is a bug, I'll file a report and attach the .mk, but I thought I'd make sure you read my follow-up first.



Log in to post a comment.