> The fundamental question though is should we allow primary, unique > CONSTRAINTS which use the index mechanism just as an implementation to be > created using the "INCLUDING INDEXES" mechanism.
Yeah, this bizarreness was foreseen and agreed to back when we set up LIKE INCLUDING CONSTRAINTS the way it was defined (ie, copying only CHECK constraints and not other things called constraints). I was never very thrilled with that definition myself, but it's a bit too late to revisit it.
Yeah this is all confusing. I believe we should remove the following TODO now that the above has been checked in:
CREATE
Have WITH CONSTRAINTS also create constraint indexes
