Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Database Access

Created: 25 Jul 2012 | 3 comments
tom.hall's picture
11 Agree
2 Disagree
+9 13 Votes
Login to vote

In the eDisclosure industry using SQL is a common way of interfacing with tools. Clearwell uses an SQL backend that currently only support engineers can access. In some situations it can be helpful to identify what Clearwell is storing on the database. My suggestion would be to keep the read/write access that support engineers have access to currently and add a support feature in the systems tab for read only access to the database.

Comments 3 CommentsJump to latest comment

interested_party's picture

I disagree.  The way to solve this would be through API access if at all.

Login to vote
dwhyte1985's picture

I agree with kunshige, a well designed and documented API would definitely be the way to go on this. Not all information is in the MySQL, it can be contained in indexes too - for this reason it'd be better (in my opinion) to tie it all together in an API.

Login to vote
Mahmood.Mir's picture

I think we need access to the database. An API is a good tool to have but that adds a learning curve for some. Where you have to learn the API calls and syntaxes. Whereas since Clearwell is using MySQL and people with SQL knowledge can easily dive in.

API will still have restrictions, which could hinder certain tasks or reports. Not to mention it will rely on the logic built by Symantec engineers. If I can access the SQL I may have a different logic to get results in a productive/efficient manner.

I'd rather have access to the database than just replying on the API. Although I have requested for an API as well knowing Symantec is keeping it really tight.



Mahmood Mir
EDD Manager

415.392.2900 | Main
415.321.8260 | Direct

Login to vote