Hi Devs/Users,
Am I the only one with a lot of layers, forgetting which one is a sql
view and which ones are true tables?
When looking for a solution for problems, I often overlook the tiny
sentence: 'Edit sql view'
below the Feature Type Details, which let you actually know:
"THIS IS A SQL VIEW LAYER!"
I understand that 'editing' the view deserves it's own page, but it
would be nice (I think) if below the Feature Type Details in the layer
page we could see the actual query/sql statement used.
Is this easy feasible? Or does the layer page not easily get this
information (or is there another reason to NOT implement this (other
then time....))?
Even better: would it not be nice to jump to the 'edit sql view'
directly from the layer list page?
I know: just do it 
But I want to know if this is easy doable, or am
I the only one having this issues...
Regards,
Richard Duivenvoorde
Hi Richard,
I cannot say I have had the same issue… personally, I would try to find ways to make it
more evident that something is a sql view without necessarily showing the entire SQL,
which on occasion can be very, very long.
Maybe a different icon? Or showing the SQL “on hover” and making the “edit sql view”
link somehow more evident? Or maybe show the sql inline with some sort of expandable toggle.
Just thinking out loud
Cheers
Andrea
···
On Wed, Oct 26, 2016 at 10:21 AM, Richard Duivenvoorde <rdmailings@anonymised.com> wrote:
Hi Devs/Users,
Am I the only one with a lot of layers, forgetting which one is a sql
view and which ones are true tables?
When looking for a solution for problems, I often overlook the tiny
sentence: ‘Edit sql view’
below the Feature Type Details, which let you actually know:
“THIS IS A SQL VIEW LAYER!”
I understand that ‘editing’ the view deserves it’s own page, but it
would be nice (I think) if below the Feature Type Details in the layer
page we could see the actual query/sql statement used.
Is this easy feasible? Or does the layer page not easily get this
information (or is there another reason to NOT implement this (other
then time…))?
Even better: would it not be nice to jump to the ‘edit sql view’
directly from the layer list page?
I know: just do it But I want to know if this is easy doable, or am
I the only one having this issues…
Regards,
Richard Duivenvoorde
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
==
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
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.