On 06/12/2014 12:06 AM, John Chilton wrote:
If anyone out there has tired using Galaxy with strictly MyISAM tables
and found it untenable - by all means please chime in.
Well, due to several reasons we are (still) using MySQL (version:
5.1.69) with only MyISAM tables. We have been
Hey Hans (and anyone else using MySQL),
Just to clarify -- MySQL doesn't have this (particular) error by default
and as long as your server default table type has not and does not change
you should be fine. I've just successfully tested MySQL using MyISAM all
the way to the current tip revision
...@gmail.com]
Sent: Thursday, June 12, 2014 9:16 AM
To: Hans-Rudolf Hotz
Cc: John Chilton; Kandalaft, Iyad; galaxy-...@bx.psu.edu
Subject: Re: [galaxy-dev] Galaxy updated botched?
Hey Hans (and anyone else using MySQL),
Just to clarify -- MySQL doesn't have this (particular) error by default and as
long
This is a follow up for those that are interested with regards to my failed
schema upgrade.
I believe I have determined why all the tables are set to use the MyISAM
engine. When I initialized galaxy on our enterprise servers, they were running
a dated version of CentOS. Hence, the OS defaults
Spent a couple hours yesterday trying to track down this - I was not
getting anywhere though and I see why now.
Well this definitely an unfortunate situation - but I think
documentation improvements are the right fix not enforcing the engine
type in sqlalchemy migrations. For one, I don't think
Hey Iyad,
I just want to second (and add slightly) to what John said here. I had
also failed to reproduce this locally, but that makes perfect sense now --
I'm glad you figured it out, and thanks for looking into this so closely
and reporting back.
Like John said, I wouldn't modify the
, 2014 10:23 AM
To: John Chilton
Cc: Kandalaft, Iyad; galaxy-...@bx.psu.edu
Subject: Re: [galaxy-dev] Galaxy updated botched?
Hey Iyad,
I just want to second (and add slightly) to what John said here. I had also
failed to reproduce this locally, but that makes perfect sense now -- I'm glad
you
-...@bx.psu.edu
Subject: Re: [galaxy-dev] Galaxy updated botched?
Hey Iyad,
I just want to second (and add slightly) to what John said here. I had also
failed to reproduce this locally, but that makes perfect sense now -- I'm
glad you figured it out, and thanks for looking into this so closely
Hi Everyone,
This is follow-up information/questions to the issue I ran into with the galaxy
June 2nd, 2014 update. I hope to receive feedback on how to proceed.
Background:
- Running Galaxy (DB Schema 118) with a MySQL 5.5 back-end
- When updating galaxy to the june 2nd
