Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Security level should be refactored to allow to use the same DB instance after renaming of user
See original GitHub issueGuys,
There is the following problem. Step by step
- Login into the OrientDB under someother (let say “myuser”)
- Rename user to for example “myuser2”
- You still can get db from OPartitionedDatabasePool under old username and password and at the same time
getMetadata().getSecurity().getUser('myuser'), of course, returns null.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Rename and Refactoring to Make Changes to your Database ...
Right-click the Products table (Products. · Right click [Products] in the script, select Refactor, and Rename. · In the New Name field, change...
Read more >Two ways to rename SQL Server database objects
Enter new name for the table Users, for example NewUsers and refresh database NewDB. In the table list it will be renamed as...
Read more >Renaming groups after creation. | Identity - Jira Atlassian
Given the dynamic nature of my environment it is very difficult for me to create the correct user group name which can be...
Read more >Refactoring Databases with SQL Prompt - Redgate Software
We'll start with the simplest database refactoring task, renaming a code module, then work our way up the ladder of complexity and risk, ......
Read more >Working with Aurora multi-master clusters - AWS Documentation
You need more than one DB instance to see the benefits of a multi-master cluster. After you create the first instance, you can...
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 Free
Top 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
Hi! My vision is that there is only one thing which can’t be changed during user’s lifecycle. I mean RID of a user. Can we try to make pooling working on RID instead of names? WDYT?
the 2.2.x is in maintainence, moving this to 3.x