On Oct 16, Jesper Noehr <[EMAIL PROTECTED]> wrote: First thing: thanks to Elefterios for your message! I was aware that the performances of SQLite were horribles, but I never thought that transactions would be such a relief! Having SQLite usable is a great enhancement.
> It's not obvious which changes you have made and to which version > even, so can I kindly ask you to submit a patch instead? Good hint for the future, but I don't need it this time: as you said a couple of months ago, the support for custom queries seems a very good base to do some really cool stuff with it - and this case fits perfectly. :-) I plan to do apply some minor changes tomorrow (if I'm still alive: damn flue) to make it easier to use, but I'm sure this situation can be handled by the command line. The fun thing is that at the time I thought it was a feature of almost no use. :-) > Also, I do believe that SQLite is a special case, True, but SQLite's benchmarks were a real shame. :-) In MySQL 5.0 for some reason I get an error with both "BEGIN TRANSACTION" and "COMMIT" - I need to look closer. In PostrgeSQL there are no improvements, as expected, and I think it will be the same with other "high-end" servers. Thanks-thanks-thanks! -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Imdbpy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
