Re: Re: BUG #5490: Using distinct for select list causes insert of timestamp string literal to fail

Farid Zidan <farid(at)zidsoft(dot)com> writes:
> I see no technical analysis in your response.

I made a clear reference to what others have been saying, and that you
have been refusing to read. I don't see any point in getting technical
again, as I'm sure you will refuse to understand what is happening to
you here.

But as you insist, let's try once more:

- your consider a bug where PostgreSQL wants to know more about the
data type you're using in the query in order to be able to enforce a
DISTINCT restriction

- other products are happy to solve the DISTINCT restriction without
any hint as far as what the datatype really is

- the error message is perfectly clear about what PostgreSQL needs from
you

- the reason why PostgreSQL wants you to give it details is clear to:
what means DISTINCT depends on the datatype, you can easily have two
different text representations of the same timestamptz, for example

- it could be considered a possible area of improvement in the system
that the SELECT part of the INSERT INTO ... SELECT ... could
determine the SELECT output columns type by looking at the INSERT
target table definition

- it would be asking for a new feature to be considered, not for a bug
to be solved: the system currently works exactly as designed.

Now if you keep wanting not to understand how the system is currently
designed, that makes it your problem, no one else.

Regards,
--
dim