Adriaan van Os wrote:
> Besides, the question is absurd. I stumble over a stone on the road,
> report it and then you ask "is there an actual use case where this is
> a problem". Why else do I report it ? What you probably wanted to ask
> is: "Apart from the missing warning along the road, couldn't
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> Aside from the apparent discrepancy between the documentation and the
>> actual behavior, is there an actual use case where this is a problem?
> No, I don't think so, and I am reluctant to adjust the documentation to
> say "or
Maarten van der Heijden wrote:
> I’m having trouble initialzing the PostGres Database 8.2 on Windows Xp
> Embedded. Installation using the windows installer is going fine until
> the initialization process is started. See below for the log. Installing
> postgres without initializing the database cl
Peter Eisentraut wrote:
> Adriaan van Os wrote:
> > >> However, min(VARCHAROID) and max(VARCHAROID) return TEXTOID as a
> > >> result type.
> > >
> > > Yea, they are internally treated as very similar types.
> >
> > But "internally treated as very similar" is still not "same as
> > argument type".
Adriaan van Os wrote:
> >> However, min(VARCHAROID) and max(VARCHAROID) return TEXTOID as a
> >> result type.
> >
> > Yea, they are internally treated as very similar types.
>
> But "internally treated as very similar" is still not "same as
> argument type". Computing requires exactness.
Aside fro
David Lloyd wrote:
> According to the ISO standard, 8601:
The date/time input format in PostgreSQL is determined by the SQL
standard, not ISO 8601.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if po
