| Feature-ID |
Desired Improvement |
Priority |
Comments |
Issue Link |
Eng Response |
| PERS-1 |
Support for a pluggable distributed persistence cache. |
P2 |
Competitive parity - offered in other persistence implementations such as Hibernate and Open JPA (Also a Community Request ). Examples: Coherence, ehCache, JBoss Cache, TerraCotta, (Shoal?). |
|
Maybe, through partnership |
| PERS-2 |
Support for statement caching |
P2 |
Many JDBC drivers support statement caching today, although PostgreSQL does not. This will improve open source benchmark results and benefit PostgreSQL users overall. Existing RFE . |
4749421 |
Yes |
| PERS-3 |
Provide an interface for a customer to supply their own connection validation method |
P2 |
Existing RFE . Example, Oracle database driver has a lightweight pingDatabase() method to validate connection |
6473767 |
Yes |
| PERS-4 |
init-sql for jdbc-connection-pool |
P2 |
Existing RFE . Allow a SQL call to be made upon connection. This would allow applications to set, for example, session character sets and isolation levels. |
6294004 |
Yes |
| PERS-5 |
Flush connection pool to recover from applications leaking connections |
P3 |
Customer RFE . (Community request ). |
6472068 |
Yes |
| PERS-6 |
Load balance across multiple connection pools |
P3 |
Improve availability. Customer request. Competitive parity. Existing RFE |
6436557 |
Yes |
| PERS-7 |
Downloadable JDBC drivers |
P2 |
Ease of use, Competitive parity . Host popular database drivers in the update center at a minimum. Ideally make user aware of online driver availability through admin console. Competitive parity would be to download the driver directly from the admin UI. Examples: PostgreSQL, MySQL, HSQLDB. |
3333 |
Yes |
| PERS-8 |
Introspect JDBC jar files for datasource name |
P3 |
Ease-of-use. Competitive parity. (RFE ) (Duplicate RFE ) |
3897 |
Yes |
| PERS-9 |
Introspect datasource to determine available properties |
P3 |
Ease-of-use. |
3322 |
Yes |
| PERS-10 |
Support Oracle RAC with Oracle thin driver |
P2 |
Current RFE . Testing/formal support |
6436556 |
Yes |
| PERS-11 |
Import connection pool content from Tomcat context.xml |
P2 |
Ease of use, migration. |
4127 |
Yes |
| PERS-12 |
Switch off connection pooling |
P3 |
Ease of use. |
4125 |
No. Need more information to understand use case. |
| PERS-13 |
Support Driver Manager based Managed Connection Factory |
P3 |
Would help arbitrary jdbc drivers that have only Driver Manager implementation. |
4126 |
Yes |
| PERS-14 |
Pool life cycle, pluggability |
P3 |
* Define pool life cycle, events, event listeners so that applications can listen to these events, control pool behavior. * Expose datastructure, pool-wait-queue, pool resizing behaviour as interfaces for multiple implementations. |
4128 |
Yes |
| PERS-15 |
Associate with thread feature to support multiple connections to be associated with the thread |
P3 |
Performance improvement |
4124 |
Yes |
| PERS-16 |
Application aware pools (Partitioned Pool) |
P3 |
Helps to improve performance of categorized applications |
3205 |
Yes |
| PERS-17 |
Implement connector for JPA |
P1 |
Required to have JPA work with v3 |
4296 |
Yes |
| PERS-18 |
Migrate CMP code to work with V3 |
P1 |
Required to have CMP work with V3 |
4297 |
Yes |
| PERS-19 |
Integrate EclipseLink as default JPA provider with V3 |
P1 |
EclipseLink will be the default provider for V3 |
4298 |
Yes |
| PERS-20 |
Support for Pluggable distributed cache |
P3 |
Often requested feature |
4299 |
Yes, create API to enable partnership opportunities |
