Thanks Anita!
On Sat, Jan 20, 2018 at 4:10 PM, Anita Graser wrote:
> I've changed the heading to better represent the content. See PR
> https://github.com/qgis/QGIS-Documentation/pull/2322
>
> Regards,
> Anita
>
>
>
> On Fri, Jan 12, 2018 at 10:57 AM, Andreas Neumann
I've changed the heading to better represent the content. See PR
https://github.com/qgis/QGIS-Documentation/pull/2322
Regards,
Anita
On Fri, Jan 12, 2018 at 10:57 AM, Andreas Neumann
wrote:
> Hi all,
>
> I agree with Richard. Thanks for referencing the PG docs. Normally,
Hi all,
I agree with Richard. Thanks for referencing the PG docs. Normally,
materialized views are not meant to be manipulated
(insert/update/delete). They are usually used to improve performance of
complex queries.
Yes - with the power of PostgreSQL one could probably somehow also
update also
Hi,
just because I stumbled upon this last month:
A materialized view is originally just a table based on a query. So you
should not update the 'view' as upon a refresh, those edits will be
overwritten.
Postgresql has an 'official' materialized view
Hi
I (or whoever wrote it) could probably have chosen a better example.
Materialised views change something that is normally read only (a view) into
something that can be treated as a writable table (with the correct
transactions being deferred to the tables that were used to create the view).
Hi,
I'm wondering about the term
"
Materialised Views (Rule based views)
" in the lesson about rules:
https://docs.qgis.org/testing/en/docs/training_manual/database_concepts/rules.html
Maybe I'm missing something, but it doesn't seem like the example has
anything to do with views. It's a