The usual way I deal with postgres - in java - is to have a connection
pool. I believe this is more or less standard in pg for performance and
it does work extremely well. I don't i'm afraid, have a pascal db
connection pool.
bd
On Fri, 07 Aug 2009 10:42:03 +0200
Graeme Geldenhuys wrote:
> Hi,
On Fri, 7 Aug 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt wrote:
Most likely the SqlDB+PostgreSQL components.
:-( I'll try and do other tests maybe via different components to see
if there is really such a huge speed penalty on my PostgreSQL setup. I
have heard that the default Pos
Graeme Geldenhuys wrote:
TestProject
|
+ Non-db tests
| + Suite1
| + Suite2
|
+ DB tests
+ Suite10
+ Suite11
"DB test" is a test decorator that sets up the DB connection. Suite10
and Suite11 both run by using the same connection which was setup before.
My test
Michael Van Canneyt wrote:
Most likely the SqlDB+PostgreSQL components.
:-( I'll try and do other tests maybe via different components to see
if there is really such a huge speed penalty on my PostgreSQL setup. I
have heard that the default PostgreSQL installation is not tuned for
performance
On Fri, 7 Aug 2009, Graeme Geldenhuys wrote:
Hi,
I'm using SqlDB (via tiOPF framework) in our applications. Our software has a
lot of db and non-db unit tests.
When I run a section of our db unit tests via SqlDB + Firebird, they complete
in about 6-7 seconds. When I run that exact same se
Hi,
I'm using SqlDB (via tiOPF framework) in our applications. Our software
has a lot of db and non-db unit tests.
When I run a section of our db unit tests via SqlDB + Firebird, they
complete in about 6-7 seconds. When I run that exact same set of db unit
tests via SqlDB + PostgreSQL, they
