RE: A problem presentaion about ECPG, DECLARE STATEMENT

Dear all,

Hi, thank you for replying.

> It seems far too late to be considering any major rewrite for v12;

> If a solid case can be made that ECPG's DECLARE STATEMENT was done
> wrong, we'd be better off to just revert the feature out of v12
> and try again, under less time pressure, for v13.

I see, I'll propose this at the next commitfest.
But I'm now considering this commit should be reverted in order to avoid
the confusion.

In oracle and postgres, this statement is used for the purpose of designating
a connection easily. If two functions have a similar goal, these ones should be
used by same way. Some specifications denoted in the document follow oracle's one.
Maybe it's not indicated in the oracle manual, and I understand it should be
discussed more.

Now, one of the major difference of usage between these DBMSs is namespace.
The current namespace unit of postgres is a process, however, oracle ensures
that SQL identifiers are unique only within the file. This means that only
postgres user cannot recycle identifier. This distinction might be inconvenient,
and it makes more confusing to change a namespace after releasing Postgres 12.

I'm now planning remake this function and change namespace unit from a process
to a file.
So I recommend you to throw this away temporally.

I want to hear your opinion.

Best Regards,
Hayato Kuroda
Fujitsu LIMITED