Edit database tables directly from CMSSiteManager.
We come upon some common situations where we need to edit some rows in the db, but don't have access to db using SQL Server Management Studio. For such scenarios editing db contents directly from Kentico panel would be very handy.
Anar
shared this idea
7 comments
-
I was refering to your second scenario which are actions that you typically do not want to do just once, and where the report makes actually more sense than an empty textbox where you need to put query every time. We will see what we can do about it, but probably later than sooner, we have other priorities for version 7.
-
Anar
commented
I was trying to point out that creating a report for running queries is not very practical.
-
You need to create a report for that, and a table in it to see the data. But you also can have a report that you always use for these kind of things, so you just prepare it and then just change the query according to your needs the next time.
-
Anar
commented
1) Sounds great.
2) Do we have to define/create new reports for that or is there a texarea where we enter our query and see query execution results right away? -
Thanks for clarification. Still, I am afraid of breaking the data, so I would prefer to solve these kinds of situations differently, how about this:
1) Be able to define the custom table that is built on existing table in DB without changing it's structure?
2) Allow for read-only view of the database objects (well technically this can be done with reporting module as well, so it may be actually better to use that right away)
-
Anar
commented
Honestly, you are right about potential dangers. But there might arise certain cases when one might need it:
1. If you have a non-Kentico table in your DB, the only chance to access data is by writing a .NET code.
2. If you want to run a SELECT query. Let say, you want to see the list of documents that are hidden in sitemap. Or if you want to list books whose author is not set where books are under different book category nodes in content tree.
...and similar scenarios that I cannot think of right now.P.S.: I want to remind you that, these are valid if your hosting environment does not provide you an SQL Server Management Studio access.
-
We are just little afraid that by putting this to the admin UI we would encourage the users to use it and potentially make their data inconsistent. Could you please tell me some specific typical scenarios when this is needed? I am not saying we won't do that, but I need some reasoning behind it to understand.
