Sven Van Caekenberghe-2 wrote
On 5 Dec 2017, at 01:00, Pierce Ng <
pierce@
> wrote:
On Sun, Nov 26, 2017 at 07:17:51PM +0100, Sven Van Caekenberghe wrote:
Added P3Client>>#timeout[:] option (thx Pierce Ng)
Thank you, Sven.
About Zdc streams. They have their own default timeout (5 seconds). I think it is not a good idea to have global timeout setting, these should be done per actual (client) instance. I like relatively short timeouts, so that I get faster feedback.
Agree. Mine was just a quick hack.
BTW, I am also interested in your experience using P3. How did it go ?
Very easy to get going.
Great !
I'm querying my server in 'batch' mode, and trying to work out the best mix of Pharo and PostgreSQL code to process the data. As we all know on this list, rapid development with Pharo is productive and fun.
Yes, it is fun.
Are you planning to implement the advanced query protocol with parameter binding?
Not immediately. It was not needed for Glorp and I doubt a bit that it would make much performance difference. Intuitively, query execution time and data transfer time feel as the most important, binding the query with parameters much less so.
Sven
Pierce
For selects, that's probably true. For inserts however (at least in my experience with Oracle), queries inserting moderately sized batches (say, 1k rows/transaction), will go from glacial to blazingly fast, when switched from 1 INSERT per row to a single insert with bindings containing data for all 1000 rows. Similar to using nextPutAll: instead of nextPut: when writing to unbuffered, flushed files, really ;) Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html