search

vazexqi / CodingSpectator

Watches and analyzes code edits in the Eclipse IDE non-invasively
http://codingspectator.cs.illinois.edu
Other
20 stars 14 forks source link

Import refactoring-problems.log into a database table #261

Open reprogrammer opened 13 years ago

reprogrammer commented 13 years ago

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 commented 13 years ago

@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).