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

Make user manager compatible to PostgreSQL #80

Open
Zulgrib opened this issue Jan 8, 2018 · 6 comments

Comments

@Zulgrib
Copy link

commented Jan 8, 2018

Expected behavior

Being able to manage users with the user manager tool

Current behavior

Error is thrown clicking the button

Failure information (for bugs)

Image of the error

Steps to reproduce

  1. Connect to PostgreSQL server as admin, I choose postgres useraccount
  2. Click the icon representing two persons in blue and green
  3. Be greeted by error

Context

  • HeidiSQL version:9.5.0.5196
  • Database system + version:PostegreSQL 9.6
  • Operating system:Windows 7 and Windows 10 (client) Windows Server 2008 R2 (server)

Failure Logs

SELECT VERSION();
/* Connecté. ID du processus : 6532 */
SET statement_timeout TO 0;
SELECT EXTRACT(EPOCH FROM CURRENT_TIMESTAMP - pg_postmaster_start_time())::INTEGER;
SELECT "nspname" FROM "pg_catalog"."pg_namespace" ORDER BY "nspname";
/* Ouverture de la session « DAYTONA-675 » */
SHOW VARIABLES LIKE E'skip_name_resolve';
/* ERREUR:  erreur de syntaxe sur ou près de « LIKE »
LINE 1: SHOW VARIABLES LIKE E'skip_name_resolve'
                       ^ */
SHOW VARIABLES LIKE E'skip_name_resolve';
/* ERREUR:  erreur de syntaxe sur ou près de « LIKE »
LINE 1: SHOW VARIABLES LIKE E'skip_name_resolve'
                       ^ */
  

@Zulgrib Zulgrib changed the title Cannot manage users on PostgreSQL Cannot manage users on PostgreSQL due to "Syntax error" Jan 8, 2018

@ansgarbecker ansgarbecker changed the title Cannot manage users on PostgreSQL due to "Syntax error" Make user manager compatible to PostgreSQL Jan 9, 2018

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jan 9, 2018

See also #17 - same for MSSQL

@Zulgrib

This comment has been minimized.

Copy link
Author

commented Jan 15, 2018

Unfortunately, i am myself a noob with postgre user management, pgadmin interface and stability are rather lacking.

Thanks for acknowledging.

Edit : I'm actually RTFMing postgre's user management, as I do not know pascal i won't be able to provide code, but can you confirm that this is what I have to look ?

@rentalhost

This comment has been minimized.

Copy link
Collaborator

commented Feb 12, 2018

Postgre seems support GRANT/REVOKE, so maybe the problem is just with the SHOW VARIABLES like in MSSQL - that should use this alternative.

ansgarbecker added a commit that referenced this issue Jul 29, 2019

Issue #80: Safely accept empty default value for probably non existin…
…g server variable "skip_name_resolve" in user manager.
@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 29, 2019

Next build has a fix for that MySQL-only syntax for getting variables, and ignores a non-existing "skip_name_resolve" variable.

But then the next query fails:

FLUSH PRIVILEGES;
/* FEHLER:  Syntaxfehler bei »FLUSH«
LINE 1: FLUSH PRIVILEGES
        ^ */

Is there some concept in PostgreSQL for reloading privileges? Or maybe this is not required at all, as I can't find any hint on the net.

@id0612

This comment has been minimized.

Copy link

commented Jul 29, 2019

PostgreSQL is not FLUSH

image

@ansgarbecker

This comment has been minimized.

Copy link
Collaborator

commented Jul 29, 2019

@id0612 please read my comment above - that's why I was asking for an alternative in PG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.