[Octave-bug-tracker] [bug #38098] package database-1.0.4 compiling issues with mkoctave

[Carnë Draug]

Update of bug #38098 (project octave):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #5:

> It may be prudent to record all this as four separate bugs:
> 1) Keeping code for postgres, mysql, sqlite, and odbc in one package called
"database" may result in something that is fragile and sub-optimal. Would
development of separate packages for each, and possibly renaming "database" as
SqUIint exclusively to use as a sandpit be a good way forward?

Considering the way that Octave Forge is currently organized, that would be
too much fragmentation.

2) a problem in liboctave-dev_3.6.3-2 gets recorded as a bug

That's the lack of oct-types.h. right? That's not a bug, it's the code in the
database package that was out of date.

3) a problem with sqlite3 gets recorded as a bug

This has been removed from the database package.

4) I have tried mysql - it fails - record this as a bug too.

This has been removed from the database package.

If my understanding is correct, the current opinion is that we shouldn't count
on SWIG to do this, as it easily breaks with new versions.

The whole database package was removed and a new version has been released
with a different API but currently only works for postgreSQL. Would be great
if you could join in the development of the new package for whatever database
system you prefer.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38098>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/