Gabriel,
I agree that we should be using a proper ORM solution, but I do not
think that the O-R mapping process can be separated from the target
application schema. I do not see why you think these are orthogonal. It
makes most sense to me to have a GUI that allows the user to navigate
their d
From: andrea.a...@gmail.com [andrea.a...@gmail.com] On Behalf Of Andrea Aime
[andrea.a...@geo-solutions.it]
Sent: Friday, 1 October 2010 5:03 PM
To: Angreani, Rini (CESRE, Kensington)
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Feature chaining vs denormal
On Fri, Oct 1, 2010 at 10:13 AM, Rini Angreani wrote:
>
> Hi Andrea,
>
> I also thought that the main reason to use feature chaining like you said,
> is to avoid managing large denormalised views. The table/view gets really
> big when you have deeply nested features (sub features that have also ha
Hi Andrea,
I also thought that the main reason to use feature chaining like you said,
is to avoid managing large denormalised views. The table/view gets really
big when you have deeply nested features (sub features that have also have
features), especially when multiple multi-valued properties ar
On Wed, Sep 29, 2010 at 4:18 PM, Gabriel Roldán wrote:
> It's too long since I don't work on app-schema as to even try to respond
> your previous questions...
>> As a final note, is there any plan to try alternative strategies to improve
>> the
>> feature chaining approach?
> I think the app-sche
How tied is the current app-schema implementation to feature chaining. I too
think that having an app-schema backed by an actual ORM is a very enticing
idea. But I don't have enough of knowledge of app-schema to know if that
would be something integrated directly into app-schema, or something that
It's too long since I don't work on app-schema as to even try to respond
your previous questions...
> As a final note, is there any plan to try alternative strategies to improve
> the
> feature chaining approach?
I think the app-schema module (since a long long time ago) should be
split into two,
Hi,
I'm looking into the application schema support and I'm wondering about the
differences between using feature chaining vs using denormalized tables/views
to create complex features.
As far as I understand feature chaining is sort of a more natural model but has
severe performance issues (N+1 q
