GSoC: Add support for importing tables from LibreOffice Base to Kexi [was: The results of your email commands]

[Jayesh Hathila]

Hi,
I am going through the code base (related to mdb) for last two days , but I
wanted to know keeping GSOC in mind do I need to focus on research part
more (and to go through most of the code base after proposal submission )
or do I need to get in touch with the code (keeping  research part after
submission ).
Regards Jayesh Hathila


On Fri, Feb 21, 2014 at 2:43 AM, Jaroslaw Staniek <staniek at kde.org> wrote:

> On 20 February 2014 21:29, Jayesh Hathila <sharma.jayesh52 at gmail.com>
> wrote:
> > Hi ,
> >
> > As you said :
> >
> > "If you look at content.xml file, it contains table/column definitions.
> > The database/script file you're mentioning contains HSQLDB or other
> > backend-specific SQL (yes, there's no respected standard). I am
> > guessing the xml is easier to parse than the specific SQL. "
> >
> > I tried to parse content.xml but the problem which I faced is that
> > content.xml does not contain every information.For e.g the samples
> > downloaded from source provided by you  (
> >
> http://www.floppybunny.org/robin/web/virtualclassroom/chap8/libreoffice_base.html
> > ) had a file under name "cons2.odb" in which by simply analyzing (after
> > unziping .odb file)  content.xml file , we don't gets necessary
> information
> > regarding- Primary key and other constraints, and also for some tables it
> > doesn't states any column at all which are originally present there in
> > database.And regarding tuples (i.e instances or values or data) its
> present
> > in "file_name/database/data" file but under some encoded scheme (till
> now I
> > couldn't found out the scheme,as I haven't thought of it much).So
> > considering above issues I think I will have to parse script file only
> > (though a little more information can be gathered from setting.xml but
> that
> > will not sufficient) .
> > If possible , I would like to have your views about my approach and
> > suggestions towards it.
> >
>
>
> Hi Jayesh,
> Thanks for the analysis.
>
> As I found no C/C++ API for HSQL, JDBC is needed to connect [1].
> Then, there's information_schema support in HSQL [2].
>
> Then, part of the research is to connect the code that reads the db
> with C/C++, without intermediate files, and ideally without extra
> processes.
>
> [1] http://hsqldb.org/doc/2.0/guide/running-chapt.html#rgc_connecting_db
> [2]
> http://stackoverflow.com/questions/7070449/how-can-i-see-table-structure-in-hsqldb
>
> --
> regards / pozdrawiam, Jaroslaw Staniek
>  Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
>  Qt for Tizen | http://qt-project.org/wiki/Tizen
>  Qt Certified Specialist | http://www.linkedin.com/in/jstaniek
> _______________________________________________
> calligra-devel mailing list
> calligra-devel at kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20140222/c2ea2648/attachment.htm>