-
Notifications
You must be signed in to change notification settings - Fork 359
Root feature: Direct query and model editor #644
Copy link
Copy link
Open
Labels
CODESome other Code related issue and it should clearly describe what it is affecting in a comment.Some other Code related issue and it should clearly describe what it is affecting in a comment.UIPertains inclusively to the User Interface.Pertains inclusively to the User Interface.enhancementSomething we do have implemented already but needs improvement upon to the best of knowledge.Something we do have implemented already but needs improvement upon to the best of knowledge.laterA long time ahead, in a galaxy near, near...A long time ahead, in a galaxy near, near...
Milestone
Metadata
Metadata
Assignees
Labels
CODESome other Code related issue and it should clearly describe what it is affecting in a comment.Some other Code related issue and it should clearly describe what it is affecting in a comment.UIPertains inclusively to the User Interface.Pertains inclusively to the User Interface.enhancementSomething we do have implemented already but needs improvement upon to the best of knowledge.Something we do have implemented already but needs improvement upon to the best of knowledge.laterA long time ahead, in a galaxy near, near...A long time ahead, in a galaxy near, near...
Currently I use external tools to do direct DB management. I'd like an interface, only available to the root user, that allows querying collections and editing the JSON version of the returned documents. Perhaps a link to the edit page on users and scripts. I'd also like an ACE editor that would execute submitted javascript on the server. I would need a DB backup and restore feature in case I screwed up anything.
This feature is low priority since I can already do this elsewhere, but I think it is essential to make the OUJS software more complete. The root user exists for a reason, not just to be the peak of the user role system, but also to manage things at the lowest level where the system lacks abstractions to prevent incorrect/dangerous behavior. There can't always be a proper interface for everything. The root should be able to handle these situations without always having to create private scripts or use external tools.