This happens with a lot of the migration scripts... I think as long as
you have the new column (I just checked, mine does) it should be fine.

On Wed, Feb 2, 2011 at 9:11 AM, Peter Cock <p.j.a.c...@googlemail.com> wrote:
> On Wed, Feb 2, 2011 at 1:27 PM, Peter Cock <p.j.a.c...@googlemail.com> wrote:
>> Should I file a bug report?
>>
>> $ sh manage_db.sh upgrade
>> 72 -> 73...
>>
>> Migration script to add 'ldda_parent_id' column to the
>> implicitly_converted_dataset_association table.
>>
>> Adding ldda_parent_id column to
>> implicitly_converted_dataset_association table failed: SQLite does not
>> support ALTER TABLE ADD FOREIGN KEY; see
>> http://www.sqlite.org/lang_altertable.html
>> done
>>
>
> Concerningly, although the upgrade says it fails, it looks like some
> of it worked:
>
> $ sh manage_db.sh db_version
> 73
>
> Shouldn't each update step be one big transaction that gets rolled
> back to leave things in a known state (in this case, schema version
> 72)?
>
> Peter
> _______________________________________________
> galaxy-dev mailing list
> galaxy-dev@lists.bx.psu.edu
> http://lists.bx.psu.edu/listinfo/galaxy-dev
>
_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev

Reply via email to