Problem upgrading DB from 72 to 73 (SQLite)
Should I file a bug report? $ sh manage_db.sh upgrade 72 -> 73... Migration script to add 'ldda_parent_id' column to the implicitly_converted_dataset_association table. Adding ldda_parent_id column to implicitly_converted_dataset_association table failed: SQLite does not support ALTER TABLE ADD FOREIGN KEY; see http://www.sqlite.org/lang_altertable.html done
On Wed, Feb 2, 2011 at 1:27 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Should I file a bug report?
$ sh manage_db.sh upgrade 72 -> 73...
Migration script to add 'ldda_parent_id' column to the implicitly_converted_dataset_association table.
Adding ldda_parent_id column to implicitly_converted_dataset_association table failed: SQLite does not support ALTER TABLE ADD FOREIGN KEY; see http://www.sqlite.org/lang_altertable.html done
Concerningly, although the upgrade says it fails, it looks like some of it worked: $ sh manage_db.sh db_version 73 Shouldn't each update step be one big transaction that gets rolled back to leave things in a known state (in this case, schema version 72)? Peter
This happens with a lot of the migration scripts... I think as long as you have the new column (I just checked, mine does) it should be fine. On Wed, Feb 2, 2011 at 9:11 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
On Wed, Feb 2, 2011 at 1:27 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Should I file a bug report?
$ sh manage_db.sh upgrade 72 -> 73...
Migration script to add 'ldda_parent_id' column to the implicitly_converted_dataset_association table.
Adding ldda_parent_id column to implicitly_converted_dataset_association table failed: SQLite does not support ALTER TABLE ADD FOREIGN KEY; see http://www.sqlite.org/lang_altertable.html done
Concerningly, although the upgrade says it fails, it looks like some of it worked:
$ sh manage_db.sh db_version 73
Shouldn't each update step be one big transaction that gets rolled back to leave things in a known state (in this case, schema version 72)?
Peter _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
On Wed, Feb 2, 2011 at 5:39 PM, Kanwei Li <kanwei@gmail.com> wrote:
This happens with a lot of the migration scripts... I think as long as you have the new column (I just checked, mine does) it should be fine.
OK, so its basically a harmless warning - I'll ignore it then. Thanks. Peter
Hello When trying to logout from our local instance of Galaxy I get the error message "This link may not be followed from within Galaxy." and cant log out. I see this using Firefox, Chrome and Camino How do I fix this so I can log out? Thanks, Nicki --------------------- Nicki Gray MRC Molecular Haematology Unit 01865 222434
Nicki Gray wrote:
Hello
When trying to logout from our local instance of Galaxy I get the error message
"This link may not be followed from within Galaxy."
and cant log out. I see this using Firefox, Chrome and Camino
How do I fix this so I can log out?
Hi Nicki, Are you using upstream authentication in the proxy server (use_remote_user = True)? --nate
Thanks, Nicki --------------------- Nicki Gray MRC Molecular Haematology Unit 01865 222434
_______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
Hi Nate In universe_wsgi.ini : # Use user provided in an upstream server's $REMOTE_USER variable use_remote_user = True Nicki On 2 Feb 2011, at 14:31, Nate Coraor wrote:
Nicki Gray wrote:
Hello
When trying to logout from our local instance of Galaxy I get the error message
"This link may not be followed from within Galaxy."
and cant log out. I see this using Firefox, Chrome and Camino
How do I fix this so I can log out?
Hi Nicki,
Are you using upstream authentication in the proxy server (use_remote_user = True)?
--nate
Thanks, Nicki --------------------- Nicki Gray MRC Molecular Haematology Unit 01865 222434
_______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
Nicki Gray wrote:
Hi Nate
In universe_wsgi.ini :
# Use user provided in an upstream server's $REMOTE_USER variable use_remote_user = True
Okay, there's another option in the config file: remote_user_logout_href This should be set to a URL which will log your users out of whatever authentication system is being used at your site. Since that's specific to each implementation I am not sure what it should be for your site. For straight HTTP Basic Authentication, it's not actually possible to log out. --nate
Nicki
On 2 Feb 2011, at 14:31, Nate Coraor wrote:
Nicki Gray wrote:
Hello
When trying to logout from our local instance of Galaxy I get the error message
"This link may not be followed from within Galaxy."
and cant log out. I see this using Firefox, Chrome and Camino
How do I fix this so I can log out?
Hi Nicki,
Are you using upstream authentication in the proxy server (use_remote_user = True)?
--nate
Thanks, Nicki --------------------- Nicki Gray MRC Molecular Haematology Unit 01865 222434
_______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
participants (4)
-
Kanwei Li -
Nate Coraor -
Nicki Gray -
Peter Cock