Abstrct
Accepts null PW, apparently no way to change PW
Maybe the account settings are hiding somewhere, but both those strike me as problems.
Because your player account is a standard Postgres user account, you can change your password with a simple ALTER USER statement. There is one other update you need to make within your user table to update the password hash first though.
Abstract (the creator) may correct this if it’s incorrect, but I believe the proper procedure for changing a password are these two statements:
UPDATE my_player SET password = MD5('your_new_password' || 'your_username') WHERE id = your_playerid; ALTER USER your_username WITH PASSWORD 'your_new_password';
That should change your password successfully.
Someone please correct me if the above is wrong!
—TE
On Aug 26, 2014, at 3:12 PM, Erik Hanson [email protected] wrote:
Maybe the account settings are hiding somewhere, but both those strike me as problems.
— Reply to this email directly or view it on GitHub.
That makes sense, but it's certainly not intuitive to someone accessing via Training Wheels.
On Tue, Aug 26, 2014 at 2:39 PM, tigereye [email protected] wrote:
Because your player account is a standard Postgres user account, you can change your password with a simple ALTER USER statement. There is one other update you need to make within your user table to update the password hash first though.
Abstract (the creator) may correct this if it’s incorrect, but I believe the proper procedure for changing a password are these two statements:
UPDATE my_player SET password = MD5('your_new_password' || 'your_username') WHERE id = your_playerid; ALTER USER your_username WITH PASSWORD 'your_new_password';
That should change your password successfully.
Someone please correct me if the above is wrong!
—TE
On Aug 26, 2014, at 3:12 PM, Erik Hanson [email protected] wrote:
Maybe the account settings are hiding somewhere, but both those strike me as problems.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub https://github.com/Abstrct/Schemaverse/issues/29#issuecomment-53476594.
It’s a SQL game. I don’t think anything about Schemaverse is meant to be intuitive…
On Aug 26, 2014, at 4:36 PM, Erik Hanson [email protected] wrote:
That makes sense, but it's certainly not intuitive to someone accessing via Training Wheels.
On Tue, Aug 26, 2014 at 2:39 PM, tigereye [email protected] wrote:
Because your player account is a standard Postgres user account, you can change your password with a simple ALTER USER statement. There is one other update you need to make within your user table to update the password hash first though.
Abstract (the creator) may correct this if it’s incorrect, but I believe the proper procedure for changing a password are these two statements:
UPDATE my_player SET password = MD5('your_new_password' || 'your_username') WHERE id = your_playerid; ALTER USER your_username WITH PASSWORD 'your_new_password';
That should change your password successfully.
Someone please correct me if the above is wrong!
—TE
On Aug 26, 2014, at 3:12 PM, Erik Hanson [email protected] wrote:
Maybe the account settings are hiding somewhere, but both those strike me as problems.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub https://github.com/Abstrct/Schemaverse/issues/29#issuecomment-53476594.
— Reply to this email directly or view it on GitHub.
Far be it for me to dictate what the game is supposed to do, but the Training Wheels setup attracted me as a relative SQL noob, as a way to learn and train.
On Tue, Aug 26, 2014 at 3:37 PM, tigereye [email protected] wrote:
It’s a SQL game. I don’t think anything about Schemaverse is meant to be intuitive…
On Aug 26, 2014, at 4:36 PM, Erik Hanson [email protected] wrote:
That makes sense, but it's certainly not intuitive to someone accessing via Training Wheels.
On Tue, Aug 26, 2014 at 2:39 PM, tigereye [email protected] wrote:
Because your player account is a standard Postgres user account, you can change your password with a simple ALTER USER statement. There is one other update you need to make within your user table to update the password hash first though.
Abstract (the creator) may correct this if it’s incorrect, but I believe the proper procedure for changing a password are these two statements:
UPDATE my_player SET password = MD5('your_new_password' || 'your_username') WHERE id = your_playerid; ALTER USER your_username WITH PASSWORD 'your_new_password';
That should change your password successfully.
Someone please correct me if the above is wrong!
—TE
On Aug 26, 2014, at 3:12 PM, Erik Hanson [email protected] wrote:
Maybe the account settings are hiding somewhere, but both those strike me as problems.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub < https://github.com/Abstrct/Schemaverse/issues/29#issuecomment-53476594>.
— Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHub https://github.com/Abstrct/Schemaverse/issues/29#issuecomment-53486835.
The route Tigereye mentioned for changing your password will work. If you do only one and not the other than some weird stuff will happen, but nothing we can't help fix too.
As for ease of use, that's just not something we are good at here. We try, and we are always happy to hear new suggestions, but it is REALLY difficult to make Schemaverse easy if the player isn't already somewhat open minded about what the user experience should be.
