,
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] (OperationalError) no such column:
history_dataset_association.extended_metadata_id
[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] (OperationalError) no such column:
history_dataset_association.extended_metadata_id
On Tue, Feb 18, 2014 at 8:30 AM
: 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 following should work
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 Cock; Galaxy Dev
*Subject:* Re: [galaxy-dev] (OperationalError) no such column
Hi all,
Earlier today I updated my development server, which uses SQLite,
and ran the update schema script (now at v118). With hindsight
there could have been a warning that I missed - because afterwards
despite updating to the galaxy-central tip, trying to use any of
the tools failed with an SQL
On Tue, Feb 18, 2014 at 8:30 AM, Peter Cock p.j.a.c...@googlemail.comwrote:
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
On Tue, Feb 18, 2014 at 1:40 PM, Dannon Baker dannon.ba...@gmail.com wrote:
On Tue, Feb 18, 2014 at 8:30 AM, Peter Cock p.j.a.c...@googlemail.com
wrote:
This fixed the history_dataset_association.extended_metadata_id
error - so is the most likely explanation a failed schema update?
Might a
