CodingSpectator icon indicating copy to clipboard operation
CodingSpectator copied to clipboard

Import refactoring-problems.log into a database table

Open reprogrammer opened this issue 13 years ago • 1 comments

We've imported parts of the captured refactoring descriptors into a CSV file and a relational database (See issues #243, #254). One way to make sense of the compilation problems due to refactorings is to import the "refactoring-problems.log" file into a table in a relational database. The timestamps in "refactoring-problems.log" and those of refactoring descriptors will allow us to relate these two pieces of data. And, importing the data into a relational database allows us to explore the data by trying out different SQL queries.

reprogrammer avatar Jul 02 '11 21:07 reprogrammer

@rajkuma1: Note that it's sufficient to convert the "refactoring-problems.log" into the CSV format. Once we generate the CSV file, we can easily import the CSV file into database tables (See issue #305).

reprogrammer avatar Aug 12 '11 03:08 reprogrammer