Re: [Geoserver-devel] Time to remove the community "script" module?

2020-12-08 Thread Ian Turton 
I wonder if we can add a this version is out of date, see here for the
current stable release type header, like postgis does?

Ian

On Tue, 8 Dec 2020, 18:02 Torben Barsballe, 
wrote:

> They've been broken for a quite a while now, and no one's stepped up yet,
> so yes, I agree it makes sense to remove them outright. +1.
> Although with how much Google likes holding on to old documentation, I
> doubt that'll do much to fix the "people getting confused" problem.
>
> Cheers,
> Torben
>
> On Mon, Dec 7, 2020 at 5:44 PM Jody Garnett 
> wrote:
>
>> +1 that would be fine.
>> --
>> Jody Garnett
>>
>>
>> On Wed, 2 Dec 2020 at 07:53, Andrea Aime 
>> wrote:
>>
>>> Hi,
>>> prompted by the discussion here:
>>>
>>> https://gis.stackexchange.com/questions/380787/how-can-i-access-scripts-in-geoserver?noredirect=1#comment622807_380787
>>>
>>> I'm wondering if it's time to just remove the script modules. They have
>>> been kicked out of the build
>>> for a while now, and no one seems to be working on them anymore. The
>>> documentation ends up confusing people.
>>> Time to drop the axe on the module?
>>>
>>> Cheers
>>> Andrea
>>>
>>> == GeoServer Professional Services from the experts! Visit
>>> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
>>> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
>>> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
>>> http://www.geo-solutions.it http://twitter.com/geosolutions_it
>>> --- *Con
>>> riferimento alla normativa sul trattamento dei dati personali (Reg. UE
>>> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail.*
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] GeoTools / GeoServer PMC meeting - 2020-12-08

2020-12-08 Thread Andrea Aime 
On Tue, Dec 8, 2020 at 7:44 PM Torben Barsballe 
wrote:

> Travis Migration
>
> *See https://github.com/geotools/geotools/wiki/Migrate-Travis-builds
>  for
> status. All have now been migrated to GitLab CI, and are running against
> the most recent PRs - everything looks to be working.*
>

Big "high five" to Brad and Mark, they took all the Travis builds and
migrated
them to GitHub actions, on all branches, in a matter of days! :-D
Awesome job folks!

Andrea

== GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
(LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GeoTools / GeoServer PMC meeting - 2020-12-08

2020-12-08 Thread Torben Barsballe 
Attending

*Torben BarsballeJody GarnettJukka Rahkonnen*Actions from last meeting:



* - [DONE] Jody: Create Ticket/Wiki for tracking Travis CI replacement
https://github.com/geotools/geotools/wiki/Migrate-Travis-builds
 - [DONE]
Andrea: ask for a December release volunteer on list - Ian will cover*Agenda


* 1. Unchecked warning GeoServer branch ready to merge2. Travis
migration/replacement3. Year-end wrap-up*Actions



* - [DONE] Thank Brad for the migration work :)*Unchecked Warning Branch


*Ready to merge: https://github.com/geoserver/geoserver/pull/4567
*Travis Migration


*See https://github.com/geotools/geotools/wiki/Migrate-Travis-builds
 for
status. All have now been migrated to GitLab CI, and are running against
the most recent PRs - everything looks to be working.*Year end wrap up

Next meeting Dec 22nd:

   -

   Bring a cuppa hot cocoa or something it has been a tough year


Community:

   -

   Reminder: vote in osgeo board elections :)
   -

   OGC meeting on today, ogcapi coordinates going official (no axis order
   is not defined)


We have not had much use for budget this year:

   -

   CITE sprint waiting on cite test infrastructure project ….
   -

   Any other ideas?


Discussion:

   -

   Jody found a library to convert markdown to html for our download
   assemblies
   -

  ... can embed SVG header

We do have a geotools SVG logo?
https://commons.wikimedia.org/wiki/File:Geotools-logo-compass.svg
>From http://svn.osgeo.org/geotools/trunk/docs/themes/geotools/static/img/
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Time to remove the community "script" module?

2020-12-08 Thread Torben Barsballe 
They've been broken for a quite a while now, and no one's stepped up yet,
so yes, I agree it makes sense to remove them outright. +1.
Although with how much Google likes holding on to old documentation, I
doubt that'll do much to fix the "people getting confused" problem.

Cheers,
Torben

On Mon, Dec 7, 2020 at 5:44 PM Jody Garnett  wrote:

> +1 that would be fine.
> --
> Jody Garnett
>
>
> On Wed, 2 Dec 2020 at 07:53, Andrea Aime 
> wrote:
>
>> Hi,
>> prompted by the discussion here:
>>
>> https://gis.stackexchange.com/questions/380787/how-can-i-access-scripts-in-geoserver?noredirect=1#comment622807_380787
>>
>> I'm wondering if it's time to just remove the script modules. They have
>> been kicked out of the build
>> for a while now, and no one seems to be working on them anymore. The
>> documentation ends up confusing people.
>> Time to drop the axe on the module?
>>
>> Cheers
>> Andrea
>>
>> == GeoServer Professional Services from the experts! Visit
>> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
>> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
>> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
>> http://www.geo-solutions.it http://twitter.com/geosolutions_it
>> --- *Con riferimento
>> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
>> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
>> circostanza inerente alla presente email (il suo contenuto, gli eventuali
>> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
>> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
>> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
>> sarei comunque grato se potesse darmene notizia. This email is intended
>> only for the person or entity to which it is addressed and may contain
>> information that is privileged, confidential or otherwise protected from
>> disclosure. We remind that - as provided by European Regulation 2016/679
>> “GDPR” - copying, dissemination or use of this e-mail or the information
>> herein by anyone other than the intended recipient is prohibited. If you
>> have received this email by mistake, please notify us immediately by
>> telephone or e-mail.*
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 17:30 UTC tomorrow

2020-12-08 Thread Jody Garnett 
Looks good, should we merge this weekend (to avoid PR going stale?)
--
Jody Garnett


On Tue, 8 Dec 2020 at 09:21, Andrea Aime 
wrote:

> Sorry I can't make it today (have to go in a few minutes), but I have
> fresh news: the unchecked warning GeoServer branch is ready to merge:
> https://github.com/geoserver/geoserver/pull/4567
>
> Cheers
> Andrea
>
>
> On Mon, Dec 7, 2020 at 7:55 PM Torben Barsballe 
> wrote:
>
>> Reminder that the next PMC meeting is scheduled for tomorrow, December 8,
>> at 17:30
>> 
>> UTC.
>>
>> You can join the meeting via Jitsi: https://meet.jit.si/GeoServerMeeting
>>
>> Cheers,
>> --
>> Torben Barsballe
>> Professional Services Engineer
>> Planet
>> torben.barsba...@planet.com
>> ___
>> GeoTools-Devel mailing list
>> geotools-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
>
> Regards, Andrea Aime
>
> == GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
> http://www.geo-solutions.it http://twitter.com/geosolutions_it
> --- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
> ___
> GeoTools-Devel mailing list
> geotools-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] travis builds migration help needed (urgent)

2020-12-08 Thread Jody Garnett 
Just wanted to thank Brad, and everyone who helped review PRs.

I think looking at the list
https://github.com/geotools/geotools/wiki/Migrate-Travis-builds list this
activity is now done!
--
Jody Garnett


On Tue, 24 Nov 2020 at 10:34, Jody Garnett  wrote:

> Important update from today's meeting, we need to migrate our travis
> builds to a new home.
>
> *urgent*
> - migrate java 8, java 11 and qa builds
> - we anticipate these being straightforward as linux environment available
> on all alternate options
>
> *strategic*
> - we have a number of database and documentation builds that need a more
> special environment. On Travis we can ask for any Docker image ...
>
> We have notes on a number of migration options (github actions, azure
> pipelines, jenkins file .. and paying travis). This is a case of the
> volunteer doing the work decideswhat is used (so if you have experience or
> would like to learn please help!)
>
> See https://github.com/geotools/geotools/wiki/Migrate-Travis-builds for
> details!
> --
> Jody Garnett
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 17:30 UTC tomorrow

2020-12-08 Thread Andrea Aime 
Sorry I can't make it today (have to go in a few minutes), but I have fresh
news: the unchecked warning GeoServer branch is ready to merge:
https://github.com/geoserver/geoserver/pull/4567

Cheers
Andrea


On Mon, Dec 7, 2020 at 7:55 PM Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, December 8,
> at 17:30
> 
> UTC.
>
> You can join the meeting via Jitsi: https://meet.jit.si/GeoServerMeeting
>
> Cheers,
> --
> Torben Barsballe
> Professional Services Engineer
> Planet
> torben.barsba...@planet.com
> ___
> GeoTools-Devel mailing list
> geotools-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>


-- 

Regards, Andrea Aime

== GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
(LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Primary key generator

2020-12-08 Thread Paul Wittle 
Corrected below as something went missing in the previous email.

From: Paul Wittle
Sent: 08 December 2020 11:58
To: Brad Hards ; geoserver-devel@lists.sourceforge.net
Subject: RE: [Geoserver-devel] Primary key generator

So after talking with my database admin colleague they felt actually doing 
index creation in the databases would not be popular with database 
administrators but if the index was held within the GeoServer system that would 
be different. I’d have to look into the sql view code to see how the identifier 
setting works there; does it effectively store a primary key index within 
GeoServer.

She felt the more useful suggestion was the simpler one of just making it 
clearer when a dataset doesn’t have a primary key.

I don’t think images work on here so I will not screenshot things but of course 
this is just a discussion to see what people think but I’d put screenshots in 
should a feature request need to be completed.

Here is a text example though:
Feature Type Details
·
Property
Type
Nillable
Min/Max Occurences
UPRN
Double
true
0/1
CONCATENATED_ADDRESS
String
true
0/1
POSTCODE
String
true
0/1
PRIMARY_CLASSIFICATION
String
true
0/1
SECONDARY_CLASSIFICATION
String
true
0/1
TERTIARY_CLASSIFICATION
String
true
0/1
QUATERNARY_CLASSIFICATION
String
true
0/1
STATUS
String
true
0/1
GEOM
Geometry
true
0/1

This is a bunch of fields in a layer but it doesn’t indicate which of those 
fields is the primary key. My suggestion is to simply highlight that 
information in the page.

In QGIS for example it would say primary key above the table or it would be 
missing if there isn’t a primary key.

So, it might look like:
   Property
Type
Nillable
Min/Max Occurences
UPRN
Double
true
0/1
CONCATENATED_ADDRESS
String
true
0/1
POSTCODE
String
true
0/1
PRIMARY_CLASSIFICATION
String
true
0/1
SECONDARY_CLASSIFICATION
String
true
0/1
TERTIARY_CLASSIFICATION
String
true
0/1
QUATERNARY_CLASSIFICATION
String
true
0/1
STATUS
String
true
0/1
GEOM
Geometry
true
0/1
PPrimary Key: UPRNry Key: UPRN

If it didn’t have one then it might look like this:
   Property
Type
Nillable
Min/Max Occurences
UPRN
Double
true
0/1
CONCATENATED_ADDRESS
String
true
0/1
POSTCODE
String
true
0/1
PRIMARY_CLASSIFICATION
String
true
0/1
SECONDARY_CLASSIFICATION
String
true
0/1
TERTIARY_CLASSIFICATION
String
true
0/1
QUATERNARY_CLASSIFICATION
String
true
0/1
STATUS
String
true
0/1
GEOM
Geometry
true
0/1
PPrimary key missing; WFS paging will not work

Thanks for your comments though 

Cheers,
Paul


From: Brad Hards mailto:br...@frogmouth.net>>
Sent: 08 December 2020 08:23
To: Paul Wittle mailto:p.wit...@dorsetcc.gov.uk>>; 
geoserver-devel@lists.sourceforge.net
Subject: RE: [Geoserver-devel] Primary key generator

I think you need to back up a little, and describe how you got to here. I’m not 
sure if this is a good idea or not, because I don’t understand the problem you 
are trying to solve.

Can you describe what you have seen, maybe in the form of a concrete, 
reproduceable example?

Brad

From: Paul Wittle 
mailto:paul.wit...@dorsetcouncil.gov.uk>>
Sent: Monday, 7 December 2020 9:17 PM
To: 
geoserver-devel@lists.sourceforge.net
Subject: [Geoserver-devel] Primary key generator

Hi everyone,

Please excuse me if this is a bad suggestion or has already been suggested but 
I was wondering if it might be worth doing a feature request to make it so that 
GeoServer can generate primary keys / indexes on database stores.

I suspect the popular view would be that it should be done on the database 
admin side but I wonder if you the people loading layers into GeoServer might 
sometime not have official database administrator roles. In theory the SQL to 
create an index is pretty simple and the database administrators can block the 
functionality by simply controlling the user account they connect with in 
GeoServer.

My thinking is that when you do an SQL view you can select the identifier but 
when you load a table or view directly you can’t. I wondered if it would be 
possible to add a similar option to the field list at the bottom of the layer 
creation page. I think this might help users to ensure their layers work with 
things like WFS 2.0 paging which I believe requires a primary key and also when 
interacting with QGIS which needs a primary key to work properly for both 
tables and views.

I also think it would be good to display the primary key as text above the 
field list and that way it could highlight when a primary key is not detected.

If people think it is a good suggestion then I will look into it more and 
perhaps try to have a go at mocking something up myself (although I’ve still 
struggled to find the time to get going with development). Of course I’ll also 
do a proper feature request but I thought I’d email out first to see how bad 
people think the idea is?

Thanks,

Paul Wittle

Re: [Geoserver-devel] Primary key generator

2020-12-08 Thread Paul Wittle 
So after talking with my database admin colleague they felt actually doing 
index creation in the databases would not be popular with database 
administrators but if the index was held within the GeoServer system that would 
be different. I’d have to look into the sql view code to see how the identifier 
setting works there; does it effectively store a primary key index within 
GeoServer.

She felt the more useful suggestion was the simpler one of just making it 
clearer when a dataset doesn’t have a primary key.

I don’t think images work on here so I will not screenshot things but of course 
this is just a discussion to see what people think but I’d put screenshots in 
should a feature request need to be completed.

Here is a text example though:
Feature Type Details
·
Property
Type
Nillable
Min/Max Occurences
UPRN
Double
true
0/1
CONCATENATED_ADDRESS
String
true
0/1
POSTCODE
String
true
0/1
PRIMARY_CLASSIFICATION
String
true
0/1
SECONDARY_CLASSIFICATION
String
true
0/1
TERTIARY_CLASSIFICATION
String
true
0/1
QUATERNARY_CLASSIFICATION
String
true
0/1
STATUS
String
true
0/1
GEOM
Geometry
true
0/1

This is a bunch of fields in a layer but it doesn’t indicate which of those 
fields is the primary key. My suggestion is to simply highlight that 
information in the page.

In QGIS for example it would say primary key above the table or it would be 
missing if there isn’t a primary key.

So, it might look like:
   Property
Type
Nillable
Min/Max Occurences
UPRN
Double
true
0/1
CONCATENATED_ADDRESS
String
true
0/1
POSTCODE
String
true
0/1
PRIMARY_CLASSIFICATION
String
true
0/1
SECONDARY_CLASSIFICATION
String
true
0/1
TERTIARY_CLASSIFICATION
String
true
0/1
QUATERNARY_CLASSIFICATION
String
true
0/1
STATUS
String
true
0/1
GEOM
Geometry
true
0/1
Primary Key: UPRN

If it didn’t have one then it might look like this:
   Property
Type
Nillable
Min/Max Occurences
UPRN
Double
true
0/1
CONCATENATED_ADDRESS
String
true
0/1
POSTCODE
String
true
0/1
PRIMARY_CLASSIFICATION
String
true
0/1
SECONDARY_CLASSIFICATION
String
true
0/1
TERTIARY_CLASSIFICATION
String
true
0/1
QUATERNARY_CLASSIFICATION
String
true
0/1
STATUS
String
true
0/1
GEOM
Geometry
true
0/1
Primary key missing; WFS paging will not work

Thanks for your comments though 

Cheers,
Paul


From: Brad Hards 
Sent: 08 December 2020 08:23
To: Paul Wittle ; 
geoserver-devel@lists.sourceforge.net
Subject: RE: [Geoserver-devel] Primary key generator

I think you need to back up a little, and describe how you got to here. I’m not 
sure if this is a good idea or not, because I don’t understand the problem you 
are trying to solve.

Can you describe what you have seen, maybe in the form of a concrete, 
reproduceable example?

Brad

From: Paul Wittle 
mailto:paul.wit...@dorsetcouncil.gov.uk>>
Sent: Monday, 7 December 2020 9:17 PM
To: 
geoserver-devel@lists.sourceforge.net
Subject: [Geoserver-devel] Primary key generator

Hi everyone,

Please excuse me if this is a bad suggestion or has already been suggested but 
I was wondering if it might be worth doing a feature request to make it so that 
GeoServer can generate primary keys / indexes on database stores.

I suspect the popular view would be that it should be done on the database 
admin side but I wonder if you the people loading layers into GeoServer might 
sometime not have official database administrator roles. In theory the SQL to 
create an index is pretty simple and the database administrators can block the 
functionality by simply controlling the user account they connect with in 
GeoServer.

My thinking is that when you do an SQL view you can select the identifier but 
when you load a table or view directly you can’t. I wondered if it would be 
possible to add a similar option to the field list at the bottom of the layer 
creation page. I think this might help users to ensure their layers work with 
things like WFS 2.0 paging which I believe requires a primary key and also when 
interacting with QGIS which needs a primary key to work properly for both 
tables and views.

I also think it would be good to display the primary key as text above the 
field list and that way it could highlight when a primary key is not detected.

If people think it is a good suggestion then I will look into it more and 
perhaps try to have a go at mocking something up myself (although I’ve still 
struggled to find the time to get going with development). Of course I’ll also 
do a proper feature request but I thought I’d email out first to see how bad 
people think the idea is?

Thanks,

Paul Wittle
[cid:image005.jpg@01D6CD58.61759400]
Business Solutions Analyst (GIS)
ICT Operations
Dorset Council
01305 228473 

dorsetcouncil.gov.uk

[cid:image007.png@01D6CD58.61759400]
[cid:image009.png@01D6CD58.61759400]

Re: [Geoserver-devel] Primary key generator

2020-12-08 Thread Brad Hards 
I think you need to back up a little, and describe how you got to here. I'm not 
sure if this is a good idea or not, because I don't
understand the problem you are trying to solve.

 

Can you describe what you have seen, maybe in the form of a concrete, 
reproduceable example?

 

Brad

 

From: Paul Wittle  
Sent: Monday, 7 December 2020 9:17 PM
To: geoserver-devel@lists.sourceforge.net
Subject: [Geoserver-devel] Primary key generator

 

Hi everyone,

 

Please excuse me if this is a bad suggestion or has already been suggested but 
I was wondering if it might be worth doing a feature
request to make it so that GeoServer can generate primary keys / indexes on 
database stores. 

 

I suspect the popular view would be that it should be done on the database 
admin side but I wonder if you the people loading layers
into GeoServer might sometime not have official database administrator roles. 
In theory the SQL to create an index is pretty simple
and the database administrators can block the functionality by simply 
controlling the user account they connect with in GeoServer. 

 

My thinking is that when you do an SQL view you can select the identifier but 
when you load a table or view directly you can't. I
wondered if it would be possible to add a similar option to the field list at 
the bottom of the layer creation page. I think this
might help users to ensure their layers work with things like WFS 2.0 paging 
which I believe requires a primary key and also when
interacting with QGIS which needs a primary key to work properly for both 
tables and views. 

 

I also think it would be good to display the primary key as text above the 
field list and that way it could highlight when a primary
key is not detected. 

 

If people think it is a good suggestion then I will look into it more and 
perhaps try to have a go at mocking something up myself
(although I've still struggled to find the time to get going with development). 
Of course I'll also do a proper feature request but
I thought I'd email out first to see how bad people think the idea is?

 

Thanks,

 


Paul Wittle 

  


Business Solutions Analyst (GIS)


ICT Operations 


Dorset Council


 

 01305 228473 


  dorsetcouncil.gov.uk

 


  

  

  

 

This e-mail and any files transmitted with it are intended solely for the use 
of the individual or entity to whom they are
addressed. It may contain unclassified but sensitive or protectively marked 
material and should be handled accordingly. Unless you
are the named addressee (or authorised to receive it for the addressee) you may 
not copy or use it, or disclose it to anyone else.
If you have received this transmission in error please notify the sender 
immediately. All traffic may be subject to recording and/or
monitoring in accordance with relevant legislation. Any views expressed in this 
message are those of the individual sender, except
where the sender specifies and with authority, states them to be the views of 
Dorset Council. Dorset Council does not accept service
of documents by fax or other electronic means. Virus checking: Whilst all 
reasonable steps have been taken to ensure that this
electronic communication and its attachments whether encoded, encrypted or 
otherwise supplied are free from computer viruses, Dorset
Council accepts no liability in respect of any loss, cost, damage or expense 
suffered as a result of accessing this message or any
of its attachments. For information on how Dorset Council processes your 
information, please see www.dorsetcouncil.gov.uk/416433
  

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel