Re: Interface MongoDB and Octave

[Mike Miller]

On Mon, Jun 06, 2016 at 16:08:11 +0200, Olaf Till wrote:
> On Mon, Jun 06, 2016 at 06:10:51AM -0700, CdeMills wrote:
> > Giulia Avallone Mendonça wrote
> > > Hello,
> > > 
> > > We are a group (of engineering students) involved in a project based on
> > > dealing with a huge amount of data. Our processing method was thought to
> > > be run by Octave, due to a list of benefits we found in this open source
> > > software. However, we have faced one lacuna when treating data from a
> > > database.
> > > 
> > > We are looking for how to connect MongoDB platform to Octave. We have
> > > already done this link using an intermediary API, and although it worked,
> > > it is still not the optimal solution for our project.
> > > 
> > > Hence, our proposal is to create a modulus able to interface directly our
> > > data stored in a MongoDB Server with Octave.  (We know that it is
> > > possible, since Matlab software has already this feature.)
> > > 
> > > We are looking forward partners to develop that modulus which we believe
> > > will bring a good contribution to the community, but also forward more
> > > information about it. In both case, don't be afraid to contact us: 
> > 
> > > address@hidden
> > 
> > > , 
> > 
> > > mohamedmahdi.soltani@
> > 
> > > .
> > 
> > Hello,
> > 
> > It's always good to have new peoples joining the Octave community.
> > 
> > Regarding your query, at this time there is a "database package" on
> > octave-forge: http://octave.sourceforge.net/database/index.html
> > 
> > This package is targeting PostgreSQL. I suggest you to think about an API
> > with a similar set of functions. Then propose the code you spoke about, f.i.
> > publishing it on GitHub, and telling us what's wrong with it and how you
> > would like to see it evolve. From a quick search, there are already C++
> > MondoDB libraries to perform query on a database; the tedious part would be
> > to translate what's returned by MongoDB in Octave values.
> > 
> > Latter, the resulting code could be integrated in the database package, this
> > would be a win-win situation for your team and for the Octave community.   
> > 
> > Regards
> > 
> > Pascal
> 
> Such code might get some 'inspiration' from the database package. But,
> though new interfaces to SQL-databases should go into the database
> package, an interface to MongoDB doesn't necessarily need to go into
> it. It's a different concept, and probably quite independent from
> SQL-related code.

Agree, this sounds like it would be a completely distinct set of
functions from the SQL database package.

Also agree with Pascal, the best way to attract contributors to help you
out is to publish what you have so far, set up a publically available
project (self-hosted, Bitbucket, GitLab, or GitHub), and let people try
it and improve it.

You also might want to refresh people's memories about your earlier post
on this topic, so we don't repeat ourselves:

https://lists.gnu.org/archive/html/help-octave/2016-04/msg00202.html

-- 
mike