Le 01/05/2009 à 23:02, Thomas Weber a écrit : > > On Fri, May 01, 2009 at 08:25:06PM +0200, Alain Baeckeroot wrote: ... > > So we made our own tools (inspired by pgnumdata 1999 D.Eddelbuettel) > > and would like to put them in octave-forge. ... > > Any comments are welcome. > > I don't like the direction this is taking[1]. If the database package > crashes routinely and you have something better, the better code should > replace the database package. We are so thinly spread that having two > packages with similar functionality is a pure waste.
So far they are not equivalent : Currently the database_1.0.1 package "works" (and crash due to swig) for postgresql, mysql and sqlite, and provide a simple (not robust nor fast) interface to those db, and have many globals var (more than 100). Our octave-postgres works only for postgres 8, it has been tested only on 32bit (but is supposed to work on 64bit too), it is fast for retrieving numbers, does db error checking, uses no global vars, and most important does not crash octave during normal flow of operations. As i'm a little biased, i think our code is better ;-) . If the only way to get our "package" on octave-forge is to replace the current one, i can try to implement something for mysql and sqlite, but it will take some time (as it is far from our needs). Alain. ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
