[ https://issues.apache.org/jira/browse/DERBY-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030175#comment-13030175 ] 

Mike Matrigali commented on DERBY-5195:
---------------------------------------

o personally I would rather not see these types of tools added as supported to the DERBY project, but rather either as unsupported
   SANE tools or as tools on top of derby in another project.  I don't think the production derby.jar should be weighed down with debugging code/tools.  
  If we decide to start "supporting" more
   tools i think they should be checked into a different part of the codeline and a different jar file.   I do think it would be nice if there
   was a place to check in unsupported tools on top of DERBY, and we have discussed it in the past but nothing came of it.  A number
   of other things come to mind like user definined functions and datatypes.  I think there have been some useful VTI's that would
   also fit into this.  
o I scanned the DataReader file and it looked like it did not depend on store at all, so would also benefit from not being in the
   store file structure so that it keeps that independence.
o I also worry if we productize these then they could be used in unintended ways and may cause problems by their use.  The intent
   is to use single user on a copy of the database, but what happens if people start running these against a  running database either
   by choice or accidently.  A lot of the existing corruptions of DERBY have come from users manipulating the log and datafiles by hand.  I
   would rather not encourage more to do so. 
o These tools basically let anyone scan a table (sort of), how does that fit in with SQL security?  

> Create tools for browsing the files in the database log directory.
> ------------------------------------------------------------------
>
>                 Key: DERBY-5195
>                 URL: https://issues.apache.org/jira/browse/DERBY-5195
>             Project: Derby
>          Issue Type: Task
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>         Attachments: ControlFileReader.java, ControlFileReader.java, LogFileReader.java, LogFileReader.java, LogFileReader.java
>
>
> It would be nice to have some tools to examine the contents of the log directory. The tools should be able to read the files in that directory without disturbing them.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira