We are looking at implementing prepared statement pooling and I have a
question if it provides any gains with a heavily updated database. I am
worried that the query plans will become stale an inefficient.
A coworker mentioned "jdbc prepared statement" != "psql or perl prepared
statement" and it is recommended for web environments (which we are).
Any suggestions would be appreciated.
Thanks,
Woody
----------------------------------------
iGLASS Networks
211-A S. Salem St
Apex NC 27502
(919) 387-3550 x813
www.iglass.net