Persistent way to configure connections #3
Description
This is actually an enhancement.
It is rather clumsy to be forced to always configure one's Connection via
the URL or the properties. In HSQLDB I had the <db>.properties file as a
form of persistent configuration.
What I suggest is that connections should have default settings persisted
in the database along with the database-specific settings (via the SET
commands). Setting transmitted via the Connection properties or the URL
(which I understand that overwrites the former) should be considered
temporary, valid only during that connection's life time.
Example:
I'm only interested in working in MVCC=true mode. The database URL
resides in a Hibernate configuration file which occasionally can be
edited by power users of the application. But I do not want to rely on
their ability to configure my database access. In fact I don't want them
to configure it.
Original issue reported on code.google.com by sulf...@gmail.com on 20 Nov 2007 at 10:29