On Jan 25, 2011, at 3:40 PM, Hans-Rudolf Hotz wrote:

Hi Davide

We were in a similar situation when we switched to external authentication. Although, only one user was affected and we were using MySQL.

I could fix it by changing the contents of the "galaxy_user" with a few sql statements. BUT, be careful! you can do a lot of damage to the database.

Could you post the sql statement? I guess that should work in the same way! Thanks d

Regards, Hans

On 01/25/2011 02:40 PM, Davide Cittaro wrote:

...

Dear all, Our local galaxy instance uses apache authentication to log users. This said, some users have no "User Name" and some other have a wrong "User name" (probably because they have been added before the apache integration). I just wonder if there's a way to modify the user names directly in the postgres database (I'm pretty sure that is possible...).

Thanks

d /* Davide Cittaro, PhD

Cogentech - Consortium for Genomic Technologies via adamello, 16 20139 Milano Italy

tel.: +39(02)574303007 e-mail: davide.cittaro@ifom-ieo-campus.it */

_______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev

/* Davide Cittaro, PhD Cogentech - Consortium for Genomic Technologies via adamello, 16 20139 Milano Italy tel.: +39(02)574303007 e-mail: davide.cittaro@ifom-ieo-campus.it */

On 01/25/2011 10:25 AM, Hans-Rudolf Hotz wrote:

...

On Jan 25, 2011, at 3:40 PM, Hans-Rudolf Hotz wrote: [...] Once again be careful with what you are doing, and don't blame me if you create a mess ;)

-1- PgAdmin ( http://www.pgadmin.org/ ) is a GUI application to manage Postgres databases - it might be a friendlier option than running direct SQL queries with 'psql'. -2- Before directly manipulation your DB, you can/should back it up with the following command: $ pg_dump -U USER DB > galaxy_db.sql If something does go wrong, you can at least revert the data to a valid state. -3- I use the following script to replicate the production database to the development database, and then it's easier to experiment with any SQL command you want without affecting the production server: ======= #!/bin/sh DATE=$(date "+%Y_%m_%d_%H%M%S") FILE="galaxy_db_prod_to_devel_${DATE}.sql.gz" DEST=/home/gordon/projects/galaxy_db_backups/ FILE="${DEST}${FILE}" echo "Dumping Prod-DB to:" echo " $FILE" echo "(Enter Galaxyprod Password)" pg_dump -c -U galaxyprod galaxyprod | sed 's/galaxyprod/galaxydevel/g' | gzip > "$FILE" || exit 1 echo echo "Dropping and re-creating Galaxy-Devel database." echo "press CTRL-C to abort or ENTER to continue." read echo "(Enter GalaxyDevel Password)": zcat "$FILE" | psql -U galaxydevel galaxydevel || exit 1 ====================== The "pg_dump -c" will add the SQL commands to drop and re-create the tables, so all tables in "galaxydevel" database are an exact copy. -gordon