my mail and in your script
> : should be migration_tmp instead of migrate_tmp;)
>
>
>
> Best regards,
>
>
>
> Pieter.
>
>
>
> *From:* Dannon Baker [mailto:dannon.ba...@gmail.com]
> *Sent:* dinsdag 22 april 2014 14:59
> *To:* Lukasse, Pieter
> *Cc:* Peter
: Peter Cock; Galaxy Dev
Subject: Re: [galaxy-dev] (OperationalError) no such column:
history_dataset_association.extended_metadata_id
Hey Pieter, sure. The sqlite database is in sqlite3 format, so you'll need to
use 'sqlite3 database/universe.sqlite' to access it.
The follow
> database
>
>
>
> Thanks and regards,
>
>
>
> Pieter.
>
>
>
> *From:* galaxy-dev-boun...@lists.bx.psu.edu [mailto:
> galaxy-dev-boun...@lists.bx.psu.edu] *On Behalf Of *Dannon Baker
> *Sent:* dinsdag 18 februari 2014 14:40
> *To:* Peter Cock
> *Cc:* Galaxy Dev
&
Thanks and regards,
Pieter.
From: galaxy-dev-boun...@lists.bx.psu.edu
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Dannon Baker
Sent: dinsdag 18 februari 2014 14:40
To: Peter Cock
Cc: Galaxy Dev
Subject: Re: [galaxy-dev] (OperationalE
On Tue, Feb 18, 2014 at 1:40 PM, Dannon Baker wrote:
> On Tue, Feb 18, 2014 at 8:30 AM, Peter Cock
> wrote:
>>
>> This fixed the history_dataset_association.extended_metadata_id
>> error - so is the most likely explanation a failed schema update?
>> Might a stale migration_tmp table have been to
On Tue, Feb 18, 2014 at 8:30 AM, Peter Cock wrote:
> This fixed the history_dataset_association.extended_metadata_id
> error - so is the most likely explanation a failed schema update?
> Might a stale migration_tmp table have been to blame?
>
Yes, I've seen this before when I've killed (or otherw
