Hey,
Martijn Faassen wrote:
It would be great if we put our community's secret gem, the ZODB, into
the limelight more, and the Google Summer of Code would be a great
opportunity. We need mentors, and fast, so if you want to mentor
someone, please sign up in this wiki page here:
Martijn Faassen schrieb:
Hey,
Martijn Faassen wrote:
It would be great if we put our community's secret gem, the ZODB, into
the limelight more, and the Google Summer of Code would be a great
opportunity. We need mentors, and fast, so if you want to mentor
someone, please sign up in this
Roché Compaan wrote:
On Mon, 2008-02-25 at 07:36 +0200, Roché Compaan wrote:
I'll update my blog post with the final stats and let you know when it
is ready.
I'll have to keep running these tests because the more I run them the
faster the ZODB becomes ;-) Would you have guessed that the ZODB
On Tue, Mar 4, 2008 at 9:27 PM, Shane Hathaway [EMAIL PROTECTED] wrote:
- Did you use optimal methods of insertion in Postgres, such as COPY?
Also note that a standard way to insert a lot of data into a relational
database is to temporarily drop indexes and re-create them after
insertion.
Lennart Regebro wrote:
On Tue, Mar 4, 2008 at 9:27 PM, Shane Hathaway [EMAIL PROTECTED] wrote:
- Did you use optimal methods of retrieval in Postgres? It is
frequently not necessary to pull the data into the application. Copying
to another table could be faster than fetching rows.
But is
On 04.03.2008, at 22:16, Shane Hathaway wrote:
Lennart Regebro wrote:
On Tue, Mar 4, 2008 at 9:27 PM, Shane Hathaway
[EMAIL PROTECTED] wrote:
- Did you use optimal methods of retrieval in Postgres? It is
frequently not necessary to pull the data into the application.
Copying
to another
