erver
Priority:
Major
Reporter:
Mauricio
On Monday, April 15, 2013 04:00:15 PM Mauricio Pazos wrote:
> Hi, working for georchestra project we have implemented the following
> approach for the issue.
>
> http://jira.codehaus.org/browse/GEOS-572
>
> Pull requset for master
>
> https://github.com/geoserver/geoserv
useful for geoserver.
--
Mauricio Pazos
--
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data
ture, if someone uses the old syntax the following warning will be
sent to the log
"WARNING: ID IN (...) is a deprecated syntax, you should use IN (...) "
cheers
--
Mauricio Pazos
www.axios.es
--
ThinkGeek and
e
> quote solution as SQL to minimise the any learning curve.
>
> Jody
I agree
--
Mauricio Pazos
www.axios.es
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Friday 28 May 2010 04:08:10 am Jody Garnett wrote:
> On 27/05/2010, at 6:55 PM, Andrea Aime wrote:
> > Mauricio Pazos ha scritto:
> >>> - have escapes to state ID is intended to be used as an attribute.
> >>> "ID" would work I guess
> >>
>
On Thursday 27 May 2010 11:53:52 am Andrea Aime wrote:
> Mauricio Pazos ha scritto:
> > On Thursday 27 May 2010 10:58:48 am Mauricio Pazos wrote:
> >> On Thursday 27 May 2010 10:48:13 am Mauricio Pazos wrote:
> >>>> Possible ways out:
> >>>> - use
On Thursday 27 May 2010 10:58:48 am Mauricio Pazos wrote:
> On Thursday 27 May 2010 10:48:13 am Mauricio Pazos wrote:
> > > Possible ways out:
> > > - use an identifier that's very unlikely or downright wrong as an
> > >attribute name. Something like @i
On Thursday 27 May 2010 10:48:13 am Mauricio Pazos wrote:
> > Possible ways out:
> > - use an identifier that's very unlikely or downright wrong as an
> >attribute name. Something like @id or ::id or id() (just making them
> >up, did not check if I'm a
ed to be used as an attribute.
>"ID" would work I guess
I like this option, it matches with SQL convention (cql is sql like), and we
could apply the same criteria for all keyword.
ID is Key
So, how could be solved the problem, if someone wants to define an CQL/ECQL
keyword as property/attribute name in a Layer?
cheers
--
Mauricio Pazos
www.axios.es
--
___
Geose
ll, my personal experience say me that if a product do not work
correctly you will see a storm of mails, telephone calls, etc. The sea looks
fine around CQL.
Analysing the constructive strategy, ECQL is reusing the CQL code, I want to
say that the error probability in ECQL is very lo
On Friday 21 November 2008 16:33:20 Andrea Aime wrote:
> Hudson ha scritto:
> > See http://hudson.opengeo.org/hudson/job/geoserver-trunk/596/changes
>
>
>
> > http://hudson.opengeo.org/hudson/job/geoserver-trunk/ws/geoserver/main/sr
> >c/main/java/org/vfny/geoserver/util/requests/readers/KvpReques
13 matches
Mail list logo
