Re: Fastest database solution

2009-02-06 Thread Curt Hash
On Fri, Feb 6, 2009 at 5:19 AM, M.-A. Lemburg wrote: > On 2009-02-06 09:10, Curt Hash wrote: >> I'm writing a small application for detecting source code plagiarism that >> currently relies on a database to store lines of code. >> >> The application has two primary functions: adding a new file to

Re: Fastest database solution

2009-02-06 Thread Curt Hash
On Fri, Feb 6, 2009 at 2:12 AM, Roger Binns wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Curt Hash wrote: > > I started out using sqlite3, but was not satisfied with the performance > > results. I then tried using psycopg2 with a local postgresql server, and > > the performance g

Re: Fastest database solution

2009-02-06 Thread M.-A. Lemburg
On 2009-02-06 09:10, Curt Hash wrote: > I'm writing a small application for detecting source code plagiarism that > currently relies on a database to store lines of code. > > The application has two primary functions: adding a new file to the database > and comparing a file to those that are alrea

Re: Fastest database solution

2009-02-06 Thread Jeroen Ruigrok van der Werven
-On [20090206 09:11], Curt Hash (curt.h...@gmail.com) wrote: >I'm writing a small application for detecting source code plagiarism that >currently relies on a database to store lines of code. > >The application has two primary functions: adding a new file to the database >and comparing a file to th

Re: Fastest database solution

2009-02-06 Thread Tino Wildenhain
Hi Curt, Curt Hash wrote: I'm writing a small application for detecting source code plagiarism that currently relies on a database to store lines of code. The application has two primary functions: adding a new file to the database and comparing a file to those that are already stored in the

Re: Fastest database solution

2009-02-06 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Curt Hash wrote: > I started out using sqlite3, but was not satisfied with the performance > results. I then tried using psycopg2 with a local postgresql server, and > the performance got even worse. SQLite is in the same process. Communication with