Hello. Ive tried read only connection, but its strange as it is writen now. When I give my database into connection list it says me that this connection already exist. Even if I have that database in different folder. Is this correct behaviour? Because it make no sense from my point of view, when I need to work with read only window I want to have option to have in connection list to connect to my database in read only or in write mode.
When I add connection in list as read and give ignore warning that this db already exist in list then it dont work. Becuase even if I open second sql window and click on connection on the same database which I have marked as not read only the window is still opened as read only.
I dont think that this system is good for standard work. I believe that better solution will be to have option in connect list to have same database twice, once as write and once as read only. And to have option to switch in windows between read only and write only mode.
And after switch it will be good to have info that my window is read only in some better visible info. Maybe down where you have info about username@dbname if there will be info read only mode...
Or maybe better as different background colour. In write mode standard white, in read only mode light green or something like that, so I as user will be able to see on first sight if Im on read only mode, so Im safe or in write mode, so I must go with cauction.
Anyway Im not sure how much read only, from user view, this mode is, when user have option to run procedure and modify data through it, I think that real read only mode must work in that way that user will be able to run just select, not execute, which can be used for modify.
I believe that read only mode can be good, because it avoid users to use commands like truncate which cannote be rollback, but in real usage it must be easier to switch between read only and write mode and this mode must be visible very well for users, so for first look onto their session window.
When I add connection in list as read and give ignore warning that this db already exist in list then it dont work. Becuase even if I open second sql window and click on connection on the same database which I have marked as not read only the window is still opened as read only.
I dont think that this system is good for standard work. I believe that better solution will be to have option in connect list to have same database twice, once as write and once as read only. And to have option to switch in windows between read only and write only mode.
And after switch it will be good to have info that my window is read only in some better visible info. Maybe down where you have info about username@dbname if there will be info read only mode...
Or maybe better as different background colour. In write mode standard white, in read only mode light green or something like that, so I as user will be able to see on first sight if Im on read only mode, so Im safe or in write mode, so I must go with cauction.
Anyway Im not sure how much read only, from user view, this mode is, when user have option to run procedure and modify data through it, I think that real read only mode must work in that way that user will be able to run just select, not execute, which can be used for modify.
I believe that read only mode can be good, because it avoid users to use commands like truncate which cannote be rollback, but in real usage it must be easier to switch between read only and write mode and this mode must be visible very well for users, so for first look onto their session window.
