On Mon, Jun 13, 2011 at 10:47 AM, Niels wrote:
> Yeah I was asking about it cause I think it can improve performance and
> functionality in app-schema.
> I didn't have time to dig deeper in to it though, and probably won't before
> the end of the project.
> Question though, If it is supported why
Yeah I was asking about it cause I think it can improve performance and
functionality in app-schema.
I didn't have time to dig deeper in to it though, and probably won't
before the end of the project.
Question though, If it is supported why would you opt-out of it?
Regards
Niels
On 13/06/11 16
On Mon, Jun 13, 2011 at 9:52 AM, Jody Garnett wrote:
> As I recall Niels was mostly interested it; and we may of missed our chance
> for his active involvement?
His last reaction was "too hard, will think about it later".
Now the too hard part has been done, so yeah I hope to see app-schema peopl
As I recall Niels was mostly interested it; and we may of missed our chance for
his active involvement? Tell you what; how about we compromise; let me fix this
1/2 geotiff thing and get a release out; and then we can turn it on.
As for the use of:
map. put(ENCODE_FUNCTIONS.key, Boolean.TRUE)
Is
On Mon, Jun 13, 2011 at 2:45 AM, Jody Garnett wrote:
> Sounds great; while I can confirm my build compiles I have not had a chance
> to try it out.
> Can you give me an example of the "flag" for the postgis docs? Unless you
> have already done so.
It's the usual thing:
map.put(ENCODE_FUNCTIONS.ke
Sounds great; while I can confirm my build compiles I have not had a chance to
try it out.
Can you give me an example of the "flag" for the postgis docs? Unless you have
already done so.
--
Jody Garnett
On Monday, 13 June 2011 at 2:18 AM, Andrea Aime wrote:
> Hi,
> I've just committed the Po
