On Fri, May 01, 2009 at 08:25:06PM +0200, Alain Baeckeroot wrote: > Hi > > we needed to acces a postgres db from octave, and tried the > database-1.01 package from octave-forge, and didnt like it: > it is slow, creates 108 global variables, and crashes : > > After installing it globally: > octave 1> pkg load database > octave 2> clear -a > panic: Segmentation fault -- stopping myself... > attempting to save variables to `octave-core'... > save to `octave-core' complete > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523085
FWIW, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490588 is a more complete reference. > After some digging, it seems that swig is the cause of this, and > we cannot fix this. Welcome to the club :) > So we made our own tools (inspired by pgnumdata 1999 D.Eddelbuettel) > and would like to put them in octave-forge. > > Currently we only read from postgresdb, we will add 'insert' very > soon, as we need this too. > > 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. [1] I didn't look at the code, so don't take this as criticism in any way. I'm merely a bystander. Thomas ------------------------------------------------------------------------------ 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
