Search Postgresql Archives

bug in 8.4 and resolved

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Member,

We found a bug in postgresql 8.4  details are follows.

 If a syntactically wrong query is made inner query of a nested query then the whole query wrongly returns a dataset instead of an error message. For example:

select * from district where statecode in (Select districtcode from state)

Please note that the attribute districtcode is not existent in the table state and if this query i.e. Select districtcode from state is executed in isolation then it correctly throws an error message. But when this incorrect query is made inner query of a nested query then the whole query wrongly returns a dataset.

This issue is observed on Postgres8.4 and is found resolved on Postgres9.1. But our issue is that our application is using postgres8.4. Where to upgrade is not possible in quick time .so is there a possible fix (patch etc.. ) for this on Postgres8.4 itself.

Thanks and Regards..
Abhinav

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux