Greg Stark writes:
> On Fri, Jul 24, 2009 at 6:02 AM, Tom Lane wrote:
>> I think the only thing we could do about it is downgrade the implicit
>> casts to "name", which seems like a cure worse than the disease ---
>> it'd interfere with searches in the system catalogs.
> We could try to avoid use
On Fri, Jul 24, 2009 at 6:02 AM, Tom Lane wrote:
> I think the only thing we could do about it is downgrade the implicit
> casts to "name", which seems like a cure worse than the disease ---
> it'd interfere with searches in the system catalogs.
We could try to avoid user-visible functions like cu
Itagaki Takahiro writes:
> The result might be a designed behavior, but is very surprising.
> What should we care for it?
I think the only thing we could do about it is downgrade the implicit
casts to "name", which seems like a cure worse than the disease ---
it'd interfere with searches in the s
"limaozeng" wrote:
> select * from t where str in (user, 'abc...ijk');
> str
> ---
> mzli
> abc...xyz
> (2 rows)
>
> only 'mzli' ought to be appeared in the result list.
Your query is interpreted as
select * from t::name whe
The following bug has been logged online:
Bug reference: 4939
Logged by: limaozeng
Email address: limaoz...@163.com
PostgreSQL version: 8.4.0
Operating system: linux-32 bit
Description:error query result
Details:
create table t(str char(200));
insert into t values '
