[ https://issues.apache.org/jira/browse/TIKA-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298670#comment-14298670 ]
Tim Allison edited comment on TIKA-1511 at 1/30/15 2:25 PM: ------------------------------------------------------------ Thank you, Nick, for reviewing this! I'll fix the wildcards...not sure how those crept in and the assertContains... I'm not happy with the added complexity of the JDBCInputStream. Bottom line: should we get rid of that option and back off to a zero-byte InputStream and grabbing the table object from the OpenContainer? That would simplify quite a bit, including detection... And, it would make this parser behave like the PST parser...I think. If we really want to add it later, we can, but simpler is better... [~lfcnassif], would you be ok with that proposal? As for another jdbc-based format, I completely agree. Can you recommend another single-file db format? Access comes to mind, but I can't find a pure Java parser that has jdbc: Jackcess (LGPL) has its own api and doesn't support jdbc. I looked briefly at derby, hsqldb, mysql, and they all seem to rely on a directory of files...I very well could have missed a single file option for those, though... Maybe h2 (MPL and EPL [licenses|http://www.h2database.com/html/license.html])? was (Author: talli...@mitre.org): Thank you, Nick, for reviewing this! I'll fix the wildcards...not sure how those crept in and the assertContains... I'm not happy with the added complexity of the JDBCInputStream. Bottom line: should we get rid of that option and back off to a zero-byte InputStream and grabbing the table object from the OpenContainer? That would simplify quite a bit, including detection... And, it would make this parser behave like the PST parser...I think. If we really want to add it later, we can, but simpler is better... [~lfcnassif], would you be ok with that proposal? As for another jdbc-based format, I completely agree. Can you recommend another single-file db format? Access comes to mind, but I can't find a pure Java parser that has jdbc: Jackcess (LGPL) has its own api and doesn't support jdbc. I looked briefly at derby, hsqldb, mysql, and they all seem to rely on a directory of files...I very well could have missed a single file option for those, though... > Create a parser for SQLite3 > --------------------------- > > Key: TIKA-1511 > URL: https://issues.apache.org/jira/browse/TIKA-1511 > Project: Tika > Issue Type: New Feature > Components: parser > Affects Versions: 1.6 > Reporter: Luis Filipe Nassif > Fix For: 1.8 > > Attachments: TIKA-1511v1.patch, TIKA-1511v2.patch, TIKA-1511v3.patch, > testSQLLite3b.db, testSQLLite3b.db > > > I think it would be very useful, as sqlite is used as data storage by a wide > range of applications. Opening the ticket to track it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)