On Wed, May 8, 2013 at 10:19 PM, Dannon Baker dannon.ba...@gmail.com wrote:
Hey Robert,
I assume this is sqlite? And, when you say you ran this without any
existing database -- was this was a completely new clone of galaxy, or did
you update a prior installation and delete
On Thu, May 9, 2013 at 11:03 AM, Peter Cock p.j.a.c...@googlemail.com wrote:
On Wed, May 8, 2013 at 10:19 PM, Dannon Baker dannon.ba...@gmail.com wrote:
Hey Robert,
I assume this is sqlite? And, when you say you ran this without any
existing database -- was this was a completely new clone
This isn't an issue with postgresql or mysql; they don't use a temporary
table for table alterations. Can you open up the sqlite database if you
still have it and see what the contents of the migrate_tmp table were?
They'll be a copy of a prior migrated table, I'm just curious what from --
it
On Thu, May 9, 2013 at 12:56 PM, Dannon Baker dannon.ba...@gmail.com wrote:
This isn't an issue with postgresql or mysql; they don't use a temporary
table for table alterations.
Oh good :)
Can you open up the sqlite database if you
still have it and see what the contents of the migrate_tmp
Hey Robert,
I assume this is sqlite? And, when you say you ran this without any
existing database -- was this was a completely new clone of galaxy, or did
you update a prior installation and delete database/universe.sqlite
manually before running?
-Dannon
On Wed, May 8, 2013 at 2:07 PM,
John Eppley wrote:
I had an error upgrading my galaxy instance. I got the following exception
while migrating the db (during step 64-65):
sqlalchemy.exc.ProgrammingError: (ProgrammingError) (1064, You have an error
in your SQL syntax; check the manual that corresponds to your MySQL
