|
379 KB
As Designed.
1.) The process to drop a user in ncluster requires you to Drop or Change the ownership of any objects owned by this user in any database. This we did not do because its to complex as the we would have to create a connection to every database to check this info.
2.) You will need to check each database and drop there permissions on objects. Again didn't due to same reason as 1.
3.) drop global permissions. This we do
4.) issue drop user DDL statement. This we do.
Connections clustering makes this visually look possible, but it would be very intensive to have code do steps 1 and 2 so we did not implement this. This issue is not just for nclusters but would also fall to all the connection clustering databases
Issue #11758 |
Closed |
Won't Fix |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |
As Designed.
1.) The process to drop a user in ncluster requires you to Drop or Change the ownership of any objects owned by this user in any database. This we did not do because its to complex as the we would have to create a connection to every database to check this info.
2.) You will need to check each database and drop there permissions on objects. Again didn't due to same reason as 1.
3.) drop global permissions. This we do
4.) issue drop user DDL statement. This we do.
Connections clustering makes this visually look possible, but it would be very intensive to have code do steps 1 and 2 so we did not implement this. This issue is not just for nclusters but would also fall to all the connection clustering databases