Hi Niels,
today during the PSC meeting the topic came out of whether
we should just drop
JDBCConfig, since:
* mails related to it are not really getting answered
* pull requests related to it are sitting there not
getting reviewed
We still have to see if there is some interested, but we
need someone to champion the module
just enough to make it worth keeping around (I'm not talking
about immediate answers, it's
a community/unsupported module, but at least some presence).
I'm also going to ping the people making pull requests.
Cheers
Andrea
On Tue, Nov 14, 2017 at 5:24 PM, Niels Charlier
<ni...@scitus.be <mailto:ni...@scitus.be>> wrote:
Hello Steve,
First I'd like to say I have been doing some work on
considerable performance improvements for jdbcconfig.
It happens to be the case that jdbcconfig doesn't take
good use of its cache and repeatedly sends the same
queries over and over again. It looks promising but I
still need to do some improvements and write some tests
and I had other work coming on top of it. But this is
definitely coming.
Also, I wrote some code in geoserver for myself to
conveniently export the jdbc catalog back to the file
system. I found a way to do this easily by firing a
bunch of catalog change events to the file system
catalog. However, I am not sure to make it easily
available to end users at this point, I assume that just
giving you the code won't be very helpful for you.
Perhaps we can work something out if you are interested.
Regards
Niels
On 09-11-17 11:02, Steve Omondi wrote:
Hi guys,
I have *JDBCConfig* enabled and connected to a Postgres
DB. I have over 500 layers spread across different
workspaces and layergroups.
After running performance tests for GetMap requests
against this configuration versus XML Catalog based
geoserver I really need to revert my catalog back to
XML in GEOSERVER DAT DIR and probably share it using NFS.
*Is their a method to export the Database Catalog
(based on JDBCConfig) back to XML Catalog?*
Kind regards,
Steve Omondi
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before
posting to this list:
- Earning your support instead of buying it, but Ian
Turton:http://www.ianturton.com/talks/foss4g.html#/
<http://www.ianturton.com/talks/foss4g.html#/>
- The GeoServer user list posting
guidelines:http://geoserver.org/comm/userlist-guidelines.html
<http://geoserver.org/comm/userlist-guidelines.html>
Geoserver-users@lists.sourceforge.net
<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users
<https://lists.sourceforge.net/lists/listinfo/geoserver-users>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the
world's most engaging tech sites, Slashdot.org!
http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list Please make sure you read
the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian
Turton: http://www.ianturton.com/talks/foss4g.html#/
<http://www.ianturton.com/talks/foss4g.html#/> - The
GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
<http://geoserver.org/comm/userlist-guidelines.html>
Geoserver-users@lists.sourceforge.net
<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users
<https://lists.sourceforge.net/lists/listinfo/geoserver-users>
--
Regards,
Andrea Aime
==GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.==Ing. Andrea Aime
<https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>@geowolfTechnical
LeadGeoSolutions S.A.S.Via di Montramito 3/A
<https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>55054
Massarosa
<https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
(LU)phone: +39 0584 962313fax: +39 0584 1660272mob: +39 339
8844549http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
<http://twitter.com/geosolutions_it>
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta
elettronica e/o nel/i file/s allegato/i sono da considerarsi
strettamente riservate. Il loro utilizzo è consentito
esclusivamente al destinatario del messaggio, per le
finalità indicate nel messaggio stesso. Qualora riceviate
questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere
alla distruzione del messaggio stesso, cancellandolo dal
Vostro sistema. Conservare il messaggio stesso, divulgarlo
anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento
contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is
intended solely for the attention and use of the named
addressee(s) and may be confidential or proprietary in
nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data
Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly
forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please
contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been
received in error. The sender does not give any warranty or
accept liability as the content, accuracy or completeness of
sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as
a result of e-mail transmission, viruses, etc.
