Hi,
I don't believe we did, can you check?
Cheers
Andrea
On Wed, Aug 26, 2015 at 9:21 AM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> Hi,
> has the default value for the system property already been switched to
> false?
> If not I can do the work, as I am back in the offi
Hi,
has the default value for the system property already been switched to
false?
If not I can do the work, as I am back in the office now.
Regards,
Mauro
2015-08-09 22:03 GMT+02:00 Jody Garnett :
> Out of the alternatives the "safest" approach seems to turn this off by
> default, and then allo
Out of the alternatives the "safest" approach seems to turn this off by
default, and then allow it to be enabled with a query hint.
--
Jody Garnett
On 9 August 2015 at 00:26, Andrea Aime wrote:
> On Sun, Aug 9, 2015 at 7:57 AM, Jody Garnett
> wrote:
>
>> Want to default the setting off for the
On Sun, Aug 9, 2015 at 7:57 AM, Jody Garnett wrote:
> Want to default the setting off for the release? And put the per table
> idea off until later...
Yep, that was my plan unless someone else has resources to work it another
way.
Cheers
Andrea
--
==
GeoServer Professional Services from the
Want to default the setting off for the release? And put the per table idea
off until later...
On Sat, Aug 8, 2015 at 10:48 PM Andrea Aime
wrote:
> On Sat, Aug 8, 2015 at 8:04 PM, Jody Garnett
> wrote:
>
>> Do need to break out an option per FeatureSource? Either by inserting
>> logic, or lookin
On Sat, Aug 8, 2015 at 8:04 PM, Jody Garnett wrote:
> Do need to break out an option per FeatureSource? Either by inserting
> logic, or looking for settings in the table metadata?
>
> The only other way I can think to get an option in is with a
> Transaction.getProperty(key) - but that does not q
Do need to break out an option per FeatureSource? Either by inserting
logic, or looking for settings in the table metadata?
The only other way I can think to get an option in is with a
Transaction.getProperty(key) - but that does not quite work since a
transaction is used for more than one feature
Hi,
it seems the usage of ST_Envelope(geom) might cause troubles after all,
and we probably don't want that enabled by default (ufff)
I was playing with a China wide OSM download, and querying a small
area on Hong Kong, after running "vacuum analyze", and ensuring
the indexes are there, gives
