Hi Mark, Thank you for the reply .. I actually came across xlSQL earlier, and I was specifically looking for any Apache licensed libraries, and xlSQL is GPLv2, which is incompatible with Apache's license as I know. Also another reason for using Apache POI is, I guess it is the most mature and actively in-development API for Excel support, e.g. having OOXML functionality.
Cheers, Anjana. On Sat, Apr 17, 2010 at 12:10 PM, MSB <[email protected]> wrote: > > Have never used it but before committing too much effort to this endeavour - > https://xlsql.dev.java.net/ > > Touts itself as "xlSQL is a JDBC Driver for Excel ( CSV, XML and other ) > document data sources. Documents can be read and written with SQL as if they > were tables in a database. In the case of Excel, xlSQL maps a directory with > Excel files to a database, workbooks to schemas, and sheets to tables. These > tables can be queried with the full SELECT syntax of either the HSQLDB or > MySQL (more to follow) SQL dialect. Native xlSQL is a rich subset of SQL for > creating, altering and populating documents ( spreadsheets ). The xlSQL Yn > codebase, although alpha, has been taken into production at numerous sites > worldwide. xlSQL has proven to be a very stable read-write SQL Excel JDBC > Driver. Continuous development efforts are aimed to explore the limits of > the XLS fileformat for storing relational data and to support other document > formats as CSV and XML. ". > > Yours > > Mark B > > > Anjana Fernando wrote: >> >> Hi, >> >> On Fri, Apr 16, 2010 at 10:28 PM, Anjana Fernando <[email protected]> >> wrote: >>> On Fri, Apr 16, 2010 at 9:25 PM, Anjana Fernando <[email protected]> >>> wrote: >>>> On Fri, Apr 16, 2010 at 9:17 PM, David Fisher <[email protected]> >>>> wrote: >>>>> One possibility is to use Derby >>>>> (http://db.apache.org/derby/papers/ApacheCon.html look into "Saucer >>>>> Separation") to read an excel sheet into an internal structure. Derby >>>>> would then provide the sql capability. >>>>> >>>>> So, I would recommend you look into incorporating POI under Derby >>>>> somehow as the database file driver. >>>>> >>>>> I were forced to do this that is what I'd do. >>>>> >>>> >>>> Thanks, will take a look :) .. >>>> >>> >>> Hi Dave, >>> >>> I'm guessing, you were referring to the table functions feature that >>> is used in Derby. After going through it a little, I see that it >>> cannot be really used to the requirement I'm suggesting. If this >>> functionality is to be used in a generic way, the behavior have to be >>> dynamic, where the Excel sheets has to be mapped to database tables >>> and so in, at the runtime. But table functions require that you give a >>> specific static function providing a result set to the external data. >>> And also the SQL syntax also will be different when referring to the >>> imported tables, but I would prefer if the user is transparent from >>> those complexities and can use SQL via a JDBC driver in a way that it >>> is talking to a database directly. >> >> To add to that, I'm guessing you cannot support DML operations with that. >> >> Anjana. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > -- > View this message in context: > http://old.nabble.com/SQL-based-data-access-for-POI-HSSF-and-POI-XSSF-tp28268341p28274406.html > Sent from the POI - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
