-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
col_is_pk variants #133
Comments
I suspect |
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
|
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: