On Fri, Oct 06, 2006 at 02:35:55AM -0500, Andrew Dunstan wrote:
> Jim Nasby wrote:
> >
> > It would be nice to denote types/aliases that are and aren't ANSI. A
> > number are marked in the docs, but it would be good to add the info
> > to that summary table.
>
> Right under the table this sentenc
Jim Nasby wrote:
>
> It would be nice to denote types/aliases that are and aren't ANSI. A
> number are marked in the docs, but it would be good to add the info
> to that summary table.
Right under the table this sentence appears:
Compatibility: The following types (or spellings thereof) are spe
On Oct 4, 2006, at 10:52 AM, Markus Schaber wrote:
Andrew Dunstan wrote:
It's not only about documenting the pure existence of the aliases
(which
was already documented in the table on the datatype TOC page),
it's also
about telling the user which of the names are the ones to avoid,
and the
Hi, Andrew,
Andrew Dunstan wrote:
>> It's not only about documenting the pure existence of the aliases (which
>> was already documented in the table on the datatype TOC page), it's also
>> about telling the user which of the names are the ones to avoid, and the
>> reasons to do so.
>
> *blink* Wh
Markus Schaber wrote:
It's not only about documenting the pure existence of the aliases (which
was already documented in the table on the datatype TOC page), it's also
about telling the user which of the names are the ones to avoid, and the
reasons to do so.
*blink* Why do any need to be a
Hi, Tom,
Tom Lane wrote:
>> Here's a small patch that adds an appropriate explanation.
>
> If we're going to document these aliases, what of float4, float8, and bool?
> Also, although the docs mention int2/int4/int8, it's more or less left
> to the reader's imagination to deduce what they are.
>
Moving to -docs
On Tue, Oct 03, 2006 at 12:13:46PM -0400, Andrew Dunstan wrote:
> Tom Lane wrote:
> >Markus Schaber <[EMAIL PROTECTED]> writes:
> >
> >>Here's a small patch that adds an appropriate explanation.
> >>
> >
> >If we're going to document these aliases, what of float4, float8, and
Tom Lane wrote:
Markus Schaber <[EMAIL PROTECTED]> writes:
Here's a small patch that adds an appropriate explanation.
If we're going to document these aliases, what of float4, float8, and bool?
Also, although the docs mention int2/int4/int8, it's more or less left
to the reader's imagi
Markus Schaber <[EMAIL PROTECTED]> writes:
> Here's a small patch that adds an appropriate explanation.
If we're going to document these aliases, what of float4, float8, and bool?
Also, although the docs mention int2/int4/int8, it's more or less left
to the reader's imagination to deduce what they
Hi, Jim,
Jim Nasby wrote:
> There's a difference between promoting and withholding info. I'd rather
> see us explicitly state which is preferred and why.
Here's a small patch that adds an appropriate explanation.
Index: doc/src/sgml/datatype.sgml
===
On Oct 2, 2006, at 6:22 PM, AgentM wrote:
On Oct 2, 2006, at 18:15 , Markus Schaber wrote:
I'm happy that the rather verbose "timestamp with time zone" has the
much nicer alias "timestamptz", however it seems that this alias
is not
documented, neither at
http://developer.postgresql.org/pgdocs
On Oct 2, 2006, at 18:15 , Markus Schaber wrote:
Hi,
I'm happy that the rather verbose "timestamp with time zone" has the
much nicer alias "timestamptz", however it seems that this alias is
not
documented, neither at
http://developer.postgresql.org/pgdocs/postgres/datatype-datetime.html
nor
Hi,
I'm happy that the rather verbose "timestamp with time zone" has the
much nicer alias "timestamptz", however it seems that this alias is not
documented, neither at
http://developer.postgresql.org/pgdocs/postgres/datatype-datetime.html
nor at http://www.postgresql.org/docs/8.1/interactive/datat
13 matches
Mail list logo
