I've managed to resolve this issue. I'm not sure how I ended up with this
issue, but in case anyone else get's hit by it, here's what I've learned:
-At version 0.6, SQLAlchemy changed the format for connecting to postgresql:
[postgresql] The "postgres" dialect is now named "postgresql"
-I so
Any feedback on this? Our local instance of Galaxy is ready to "go live" and
this is one of the remaining issues keeping us from more wide-spread usage.
Can anyone confirm that I should be using
scripts/cleanup_datasets/cleanup_datasets.py when I'm using postgresql? Are
there any limits on t
Posting to galaxy-...@bx.psu.edu to give the question better exposure to
the development community.
Please _remove the galaxy-u...@bx.psu.edu mailing list from all replies_
- we want to avoid double posts.
For discussion of
local Galaxy instances and the Galaxy source code, please
use the Gala