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

[anonymous]

Follow-up Comment #2, bug #38098 (project octave):

It seems to be workable, with one bug outstanding on sqlite3 than can be
worked around. There may be a more serious bug in liboctave-dev_3.6.3-2
(it seems to rely on some old code from 3.2.4 to be present to compile,
possibly something to do with /configure)

I ran some tests with my version of octave, results are as follows:
Postgres - 'empty' lists the commands, 'basic' tests run, and results seem
good.
sqlite3 - 'empty' lists the commands, no other tests run because the needed
database tables, user, and passwords are not yet set up.
mysql - configure fails to detect my installation (see below)
odbc - configure fails to detect my installation - that may be correct.

I doubt I have the skills to support the package, but at least the option
of installing and running this package is there. I guess it is bad timing on
my part if "database" is ditched.

###############
> development version
That code may make mysql useable.  I have not yet downloaded the development
version. I may do that in the next day or two.

I'd need to give some further thought to planning development. Until now,
I merely wanted to see how useful a database interface via octave could be.
I'd see my priorities as follows:
a) compare operation of some existing programs using octave, perl and
postgres.
b) resolve the bug? in liboctave-dev_3.6.3-2
c) test database-1.0.4 with sqlite3, mysql, and odbc to 'basic' level
d) resolve bug with sqlite3

I've listed priorities for information. If you think I can do some _simple_
tasks that may help, please ask.


    _______________________________________________________

Reply to this item at:

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

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