Michael Meskes wrote:
> While ecpg may not be the choice for new applications, there are a lot
> of legacy applications out there that need ecpg to be migrated to
> PostgreSQL.
2016 is a good time to rewrite them. ;)
I think Postgres will be more likely if it would be a little less concerned
about compatibility IMHO.
But I will not insist. My problem with ecpg I decided.
Thanks.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
