Name of role/user is not quoted in DDL
See original GitHub issueSystem information:
- DBeaver version The last
- Additional extensions No
Connection specification:
- Database name and version PostgreSQL, Firebird, Oracle, maybe some other
Describe the problem you’re observing:
After
CREATE USER "John Doe";
CREATE USER "Вася Пупкин";
See DDL for role/user. If there is space in name of role or user, there is no quoting => invalid DDL.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Create PostgreSQL ROLE (user) if it doesn't exist
And you cannot execute dynamic DDL statements in plain SQL. ... Quoting is handled properly, so no special character in password can cause ......
Read more >hive with SQL Standard-based Authorization - 111505
hi, im trying to setup SQL Standard-based Authorization based on the - 111505.
Read more >CREATE USER - Snowflake Documentation
Name that the user enters to log into the system. Login names for users must be unique across your entire account. A login...
Read more >Fixed Database Role - an overview | ScienceDirect Topics
sp_droprolemember 'role', 'user', Removes a login from a database role. sp_helprole, Returns a basic list of all database roles, including fixed database ...
Read more >SQL Features for Managing Access - Firebird
The SQL set of DDL commands for managing user accounts has been enhanced in Firebird ... previously set tags if they are not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yep, you it’s true about User<>Schema. But we don’t have user’s DDL tab and as a schema, he is quoted.
So. This bug is for PostgreSQL.
verified