I can imagine use cases where you'd want jdbcconfig, but not
particularly need jdbcstore.
I understood jdbcconfig was made primarily for scaling, but jdbcstore is
really only that useful with clustering.
Jdbcstore is theoretically possible without jdbcconfig (although you'd
have to load the module, you can configure it as disabled) but that
seems silly to me (the catalog would then be stored in the jdbcstore db
instead of its own, which would not scale well).
On 09-12-15 18:03, Jody Garnett wrote:
+1 from me.
Q: Is it worth a new module or should it be merged in with JDBCConfig?
(Like would you ever want one without the other?)
--
Jody Garnett
On 9 December 2015 at 08:39, Niels Charlier <[email protected]
<mailto:[email protected]>> wrote:
We'd like to create a new community module: jdbcstore, which
implements
the resource store (normally the data directory) as a jdbc
database with
BLOBs in it.
Kind Regards
Niels
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
