`has_pk(:schema, :table)` Not defined about pgtap

[aklaver]

All right some time in pgtap.sql.in showed me what is going on. Due to function overloading the only form that automatically sets the description is has_pk( :table ). I was misunderstanding and thought :description was optional in all cases. I now know that the function signatures need to be fully followed for the different forms.

[theory]

Oh well perhaps we're missing has_pk(:schema, :table). If we had it you could make sure it's called instead of has_pk(:schema, :desc) by specifying the type:

SELECT has_pk('utility', 'eqpt_model_info'::name);

[aklaver]

Yeah, I could see that being helpful. Would that fill in the missing :desc like SELECT has_pk('eqpt_model_info');?

[theory]

Would that fill in the missing :desc like SELECT has_pk('eqpt_model_info');?

Yes, exactly.

[aklaver]

Thanks.