You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect col_is_pk( name, name, name) could clash with col_is_pk( name, name, text). How can you distinguish: col_is_pk( 'public', 'foo', 'id' )
from col_is_pk( 'foo', 'id', 'id is not pk' ); ?
fluca1978
added a commit
to fluca1978/pgtap
that referenced
this issue
Oct 2, 2018
This allows for the automatic overloading of the function, implementing
therefore the col_is_pk( name, name, name[] ) as requested in issue theory#133.
See issue theory#133.
There are a few other examples of functions with potentially-conflicting signatures. In those cases, we suggest that some of the params be cast to avoid the conflicts. See the docs for has_sequence for an example. They say:
If you find that the function call seems to be getting confused, cast the sequence to the NAME type:
There should also be
(name, name, name)
and(name, name, name[])
versions ofcol_is_pk
. Those versions already exist forcol_is_unique()
.The text was updated successfully, but these errors were encountered: