Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALTER USER SET PASSWORD doesn't recognise username #2844

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

ALTER USER SET PASSWORD doesn't recognise username #2844

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-07-19 19:15:36 +0200
From: @grobian
To: SQL devs <>
Version: 11.3.3 (Apr2011-SP1) [obsolete]

Last updated: 2011-07-29 10:52:43 +0200

Comment 15975

Date: 2011-07-19 19:15:36 +0200
From: @grobian

sql>ALTER USER SET PASSWORD 'anders' USING OLD PASSWORD 'monetdb';
SQLException:sql.catalog:ALTER USER: no such user '�'

i.e. garbage, it should see the current user instead.

Comment 15976

Date: 2011-07-19 19:37:39 +0200
From: @grobian

Changeset 0f9f5c7b727c made by Fabian Groffen fabian@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f9f5c7b727c

Changeset description:

sql_alter_user: recognise str_nil as NULL

After ALTER USER statements have been made to go through a MAL program,
the user argument no longer would be NULL, but nil:str.  As such, the
current user (== NULL) was no longer found, making it impossible to
change the password for the administrator (== monetdb) password.
Accept str_nil as alternative for NULL, fixes bug #2844.

Comment 15977

Date: 2011-07-19 19:38:57 +0200
From: @grobian

per comment 1

Comment 16006

Date: 2011-07-29 10:52:43 +0200
From: @sjoerdmullender

The Apr2011-SP2 bugfix release is out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant