Hi Leandro
brilliant! - adding the line manually did indeed fix the problem and I
could remove the re-activate line 36 and 37 in ~/lib/galaxy/app.py
Thank you very much!
now have to find out why this line was not inserted in the first place
Hans
On 04/24/2012 06:04 PM,
Hi everybody
I usually don't like people sending the same e-mail several times, so I
apologize for just doing this, since nobody has replied to last week's
email so far.
Although, we do not encounter any problems at the moment, I fear we will
run into problems at a later stage (ie at the
Hello Hans,
I've stayed out of this one due to your use of mysql which I cannot personally
support as I restrict my environment to sqlite and postgres. However, assuming
this is not a problem restricted to mysql, can you try the following from your
Galaxy installation directory (you should
Hi Greg
I was hoping to avoid thisI will let you know the outcome.
On a related note: are there any plans to migrate all MySQL users to
postgres? It is probably easier in the longterm.maybe a topic we can
discuss in Chicago.
Thank you very much for your reply
Regards, Hans
On
Hi hans,
On Apr 24, 2012, at 10:49 AM, Hans-Rudolf Hotz wrote:
Hi Greg
I was hoping to avoid thisI will let you know the outcome.
This really shouldn't be a problem, the migration scripts for 91, 92 simply
create new tables with 91 generating new data to insert, and 92 inserting a
Dear Hans,
//galaxy_dist/eggs/sqlalchemy_migrate-0.5.4-py2.6.egg/migrate/versioning/schema.py,
line 42, in _load
data = list(result)[0]
IndexError: list index out of range
This error is because SQLAlchemy cannot load the controlled schema
version info from the DB, the result is empty, so
Hi Leandro
Thank you very much for your e-mail. Indeed, the 'migrate_tools' table
is empty:
mysql select * from galaxy_xenon1.migrate_version;
+---+--+-+
| repository_id | repository_path | version |
Hi
We are in the process of migrating our Galaxy servers to the current
March 12, 2012 release ('6799:40f1816d6857').
We have encountered two issues, which I guess are related:
If I restart the server, I get:
galaxy.model.migrate.check INFO 2012-04-16 09:24:50,391 At database
version 93
