Re: [Geoserver-devel] Switching GeoServer to ECQL?

Mauricio Pazos ha scritto: >> Pity that "ID" cannot be used, it would have been backwards compatible >> (I think). > Yes, it could be a problem, I am thinking in this cases to query by fid > "ID" like "city.1" > "ID" = 1 > ID in (...) > I think it could be confuse Yeah, I agree it could be a bit

Re: [Geoserver-devel] Switching GeoServer to ECQL?

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 > >> > >> I like this option, it matches with SQL convention

Re: [Geoserver-devel] Documentation guide?

On 27/05/10 22:52, Mike Pumphrey wrote: >> Thanks, I see it now. Perhaps moving it into the trunk section, with the >> other trunk docs? I think the reason I missed it was that I expected so >> see it in the trunk section. > > http://docs.geoserver.org/trunk/en/docguide/ > It is in the trunk sectio

Re: [Geoserver-devel] Switching GeoServer to ECQL?

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 >> I like this option, it matches with SQL convention (cql is sql like), and we >> could apply the same criteria for all

Re: [Geoserver-devel] polish language

Hi Fernando, There's a community module I started some time ago intended to aid in translating the GeoServer UI I've a bunch of uncommitted stuff though that still haven't the time to get into good shape. Yet, if you're inter

Re: [Geoserver-devel] Documentation guide?

> Thanks, I see it now. Perhaps moving it into the trunk section, with the > other trunk docs? I think the reason I missed it was that I expected so > see it in the trunk section. http://docs.geoserver.org/trunk/en/docguide/ It is in the trunk section. :) It's just its own project. Since I've r

Re: [Geoserver-devel] polish language

Hi Fernando, There in svn along with the geoserver sources. http://svn.codehaus.org/geoserver/trunk/src/web/ Under that url there are a number of properties files: ./core/src/main/java/GeoServerApplication.properties ./demo/src/main/java/GeoServerApplication.properties ./gwc/src/main/java/Ge

Re: [Geoserver-devel] polish language

Hi Justin, Where are these files? I like to do the translation into Portuguese. Best Regards, Fernando Quadro 2010/5/27, Justin Deoliveira : > Hi Grzegorz, > > That is great. New language contributions are always welcome. The best > way would probably be to create an issue in JIRA and attach th

Re: [Geoserver-devel] polish language

Hi Grzegorz, That is great. New language contributions are always welcome. The best way would probably be to create an issue in JIRA and attach the files there. As for the translating gwc. Which parts are you attempting to localize? The ui that is part of geoserver, or the UI that gwc ships int

[Geoserver-devel] [jira] Created: (GEOS-3986) JDBC SQLException when publishing Oracle Spatial layer via Oracle extension JNDI datasource

JDBC SQLException when publishing Oracle Spatial layer via Oracle extension JNDI datasource --- Key: GEOS-3986 URL: http://jira.codehaus.org/browse/GEOS-3986 Proj

Re: [Geoserver-devel] Switching GeoServer to ECQL?

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 an identifier that's very unlikely or downright wro

Re: [Geoserver-devel] Switching GeoServer to ECQL?

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 an identifier that's very unlikely or downright wrong as an attribute name. Something like @id or ::id or id

[Geoserver-devel] Hudson build is back to normal: geoserver-2.0.x-nightly #214

See -- ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourcefo

[Geoserver-devel] [jira] Created: (GEOS-3985) RetypeDataStore does not properly handle the case of a feature type renamed to a target name that is also available the native name of another feature typ

RetypeDataStore does not properly handle the case of a feature type renamed to a target name that is also available the native name of another feature type --

Re: [Geoserver-devel] Switching GeoServer to ECQL?

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 @id or ::id or id() (just making them > > >

Re: [Geoserver-devel] Switching GeoServer to ECQL?

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 actually introducing other problems with

Re: [Geoserver-devel] Switching GeoServer to ECQL?

Mauricio Pazos ha scritto: >> - have escapes to state ID is intended 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 Keyword, "ID" is attribute > LI

Re: [Geoserver-devel] Switching GeoServer to ECQL?

On Thursday 27 May 2010 10:05:56 am Andrea Aime wrote: > > Actually, there are two different symbols: "LIKE" and LIKE. So, in the > > SQL language "LIKE" is an identifier and LIKE is the keyword. > > What happens in ECQL in that respect? Is there a way to use a keyword > as an identifier? No, it i

[Geoserver-devel] Application schema download now automated

Rob, in addition to conscripting more GeoServer developers, I have now completed app-schema support for automated downloading and caching of application schemas. The documentation should soon be automatically generated: http://docs.geoserver.org/trunk/en/user/data/app-schema/app-schema-resoluti

[Geoserver-devel] osgeo/Geoserver flyer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, the Geoserver project is currently in the OSGeo incubation process and it would be great if there would also be a flyer for the project. Other OSGeo project already have some documents which can be used at fairs or congresses. The repository

[Geoserver-devel] polish language

Hi, I have files with polish translations of GUI (based on v.2.0.1). Where should I send them? There is one exception. I can't find file with strings for GWC. Is it possible to localize it? Grzegorz -- View this message in context: http://old.nabble.com/polish-language-tp28682478p28682478.htm

Re: [Geoserver-devel] Switching GeoServer to ECQL?

Mauricio Pazos ha scritto: > On Wednesday 26 May 2010 06:04:28 pm Andrea Aime wrote: >> ID IN ('states.1','states.2') and STATE_NAME like 'I%' >> >> and they all worked fine. Only concern is that ID might conflict with >> an existing field. > Let me open the debate in this list. > > In general,

Re: [Geoserver-devel] Switching GeoServer to ECQL?

On Wednesday 26 May 2010 06:04:28 pm Andrea Aime wrote: > ID IN ('states.1','states.2') and STATE_NAME like 'I%' > > and they all worked fine. Only concern is that ID might conflict with > an existing field. Let me open the debate in this list. In general, you will have problem in ECQL/CQL if yo