Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > On m?n, 2011-01-24 at 15:07 -0500, Bruce Momjian wrote:
> > > Now that our /contrib documentation is in our SGML manual, I want to
> > > update our docs to link to the actual contrib module documentation,
> > > rather than just referencing contrib/
Peter Eisentraut wrote:
> On m?n, 2011-01-24 at 15:07 -0500, Bruce Momjian wrote:
> > Now that our /contrib documentation is in our SGML manual, I want to
> > update our docs to link to the actual contrib module documentation,
> > rather than just referencing contrib/module_name. We used to have t
On mån, 2011-01-24 at 15:07 -0500, Bruce Momjian wrote:
> Now that our /contrib documentation is in our SGML manual, I want to
> update our docs to link to the actual contrib module documentation,
> rather than just referencing contrib/module_name. We used to have to do
> that when we only had REA
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> I still think that a link to the contrib module's page would be a good
> >> thing to provide here.
>
> > Yep, but how to do it in a clear way?
>
> The parenthetical wording we just discussed seemed fine to me.
OK, done with the at
Bruce Momjian writes:
> Tom Lane wrote:
>> I still think that a link to the contrib module's page would be a good
>> thing to provide here.
> Yep, but how to do it in a clear way?
The parenthetical wording we just discussed seemed fine to me.
regards, tom lane
--
Sent
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> That's not just awkward, but flat wrong, because the link points to
> >> documentation of the module not the function.
>
> > The tag for the dblink module is:
>
> >
>
> > the function's tag is:
>
> >
>
> > so I believ
Bruce Momjian writes:
> Tom Lane wrote:
>> That's not just awkward, but flat wrong, because the link points to
>> documentation of the module not the function.
> The tag for the dblink module is:
>
> the function's tag is:
>
> so I believe the text in the patch is correct. (Ye
Tom Lane wrote:
> Bruce Momjian writes:
> > That is an interesting case. I didn't mention "module" here because
> > above this ia a dblink() function call, and we are referencing the
> > function call in the text. I couldn't figure out how to mention
> > "module" here without making the text mor
Bruce Momjian writes:
> That is an interesting case. I didn't mention "module" here because
> above this ia a dblink() function call, and we are referencing the
> function call in the text. I couldn't figure out how to mention
> "module" here without making the text more complex. I thought of:
Josh Kupershmidt wrote:
> On Mon, Jan 24, 2011 at 10:33 PM, Bruce Momjian wrote:
> > Suggestions?
>
> For this bit:
>
> *** 686,693
> AS t1(proname name, prosrc text)
> WHERE proname LIKE 'bytea%';
>
> ! The dblink function executes a remote query (see
> ! contrib
On Mon, Jan 24, 2011 at 10:33 PM, Bruce Momjian wrote:
> Suggestions?
For this bit:
*** 686,693
AS t1(proname name, prosrc text)
WHERE proname LIKE 'bytea%';
! The dblink function executes a remote query (see
! contrib/dblink). It is declared to return
rec
[ repost with compressed diff]
Tom Lane wrote:
> Bruce Momjian writes:
> > Now that our /contrib documentation is in our SGML manual, I want to
> > update our docs to link to the actual contrib module documentation,
> > rather than just referencing contrib/module_name. We used to have to do
> >
Bruce Momjian writes:
> Now that our /contrib documentation is in our SGML manual, I want to
> update our docs to link to the actual contrib module documentation,
> rather than just referencing contrib/module_name. We used to have to do
> that when we only had READMEs, but now we can do better.
Now that our /contrib documentation is in our SGML manual, I want to
update our docs to link to the actual contrib module documentation,
rather than just referencing contrib/module_name. We used to have to do
that when we only had READMEs, but now we can do better.
Patch attached, and I have a gi
14 matches
Mail list logo
