man, 04 05 2009 kl. 21:38 +0200, skrev Thomas Weber: > So, if the current database package crashes for all three supported > databases, I'm all in favor of wiping it completely and starting just > with PostgreSQL. This is my opinion only, at least Soren should speak up > about that.
I'd rather not have an opinion on this subject as I don't use the database bindings. I agree with your reasoning, that it is better to have one good package than many poor ones, though. So, what is the current status of the database package? I get the impression that it easily crashes. Is this due to some fundamental design decision or is "just" a few easy bugs that should be ironed out? Alain, mentioned that it was slow (compared to his code). Is this a real-world issue? I assume people interacting with databases often do so because they have huge amounts of data, which I guess translates into "speed matters". Is this true? In general, what is the use-case for database interaction? Would it be sensible to consider wrapping something like "libgda" in a package, such that we would only need to interact with one API? Would this fulfil our needs? As you can tell, I'm more confused than knowledgeable, which is why I'd rather not have an opinion on the design choices made. Søren ------------------------------------------------------------------------------ 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
