Обсуждение: Typo in Documentation for Version 12 Section 40.3
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/rules-materializedviews.html Description: Hi all, This is the link to the page which has a typo. https://www.postgresql.org/docs/10/rules-materializedviews.html. In the line below the fourth code snippet square, it says: >>> If people want to be able to quickly graph historical sales data, ... This sentence doesn't make sense. I think it should be: --- If people want to be able to quickly grab/obtain/get historical sales data, ... Regards, Yushan
> On 9 Jan 2020, at 09:05, PG Doc comments form <noreply@postgresql.org> wrote: >>>> If people want to be able to quickly graph historical sales data, ... > > This sentence doesn't make sense. I think it should be: > > --- If people want to be able to quickly grab/obtain/get historical sales > data, ... I'm not a native english speaker, but I'm pretty sure that sentence is correct. "graph" in this context refers to generating a graph of the data, which is made quite clear in the sentence below the codesnippet: "This materialized view might be useful for displaying a graph in the dashboard created for salespeople." cheers ./daniel
I partially agree. But with the context, it doesn't assume we want `view<->visualize` the data. It also says:
>> Another use for a materialized view is to allow faster access to data brought across from a remote system through a foreign data wrapper.
It is talking about 'the view' not the graph.
Yushan
Daniel Gustafsson <daniel@yesql.se> 于2020年1月9日周四 下午5:16写道:
> On 9 Jan 2020, at 09:05, PG Doc comments form <noreply@postgresql.org> wrote:
>>>> If people want to be able to quickly graph historical sales data, ...
>
> This sentence doesn't make sense. I think it should be:
>
> --- If people want to be able to quickly grab/obtain/get historical sales
> data, ...
I'm not a native english speaker, but I'm pretty sure that sentence is correct.
"graph" in this context refers to generating a graph of the data, which is made
quite clear in the sentence below the codesnippet:
"This materialized view might be useful for displaying a graph in the
dashboard created for salespeople."
cheers ./daniel
--
--------------------------------------------------------------------------------
Apologize to any possible reply delay for time differences.
对于任何由于时差未能及时回复邮件的情况表示抱歉。
> On 9 Jan 2020, at 10:34, Octopus ZHANG <zhangysh1995@gmail.com> wrote: Please don't top-post on the mailinglists. > I partially agree. But with the context, it doesn't assume we want `view<->visualize` the data. It also says: > > >> Another use for a materialized view is to allow faster access to data brought across from a remote system through aforeign data wrapper. > > It is talking about 'the view' not the graph. My reading is that it's referring to the usecase for the view, and that is to use the summarized data in a graph. So I think it's correct. cheers ./daniel
Daniel Gustafsson <daniel@yesql.se> writes: >> On 9 Jan 2020, at 10:34, Octopus ZHANG <zhangysh1995@gmail.com> wrote: >> I partially agree. But with the context, it doesn't assume we want `view<->visualize` the data. It also says: >>> Another use for a materialized view is to allow faster access to data brought across from a remote system through a foreigndata wrapper. >> It is talking about 'the view' not the graph. > My reading is that it's referring to the usecase for the view, and that is to > use the summarized data in a graph. So I think it's correct. The first sentence uses "graph" as a verb, while the next one uses "graph" as a noun. Both are correct English, but I can understand that the inconsistency might confuse non-native speakers. Not sure if it's worth changing. regards, tom lane