Why was NpgsqlException.ConstraintName property removed?
<p>I am wondering why the .ConstraintName property on NpgsqlException was removed. I noticed it no longer existed after upgrading to npgsql 3.1.8. (I had not upgraded npgsql in a long time) </p>

<p>I found .ConstraintName to be very helpful, because I had quite a bit of my code dependant upon the constraint name (e.g. I was using .ConstraintName to generate "non technical" error messages to the user.)</p>

<p>Does this mean I need to manually parse out the constraint name each time from NpgsqlException.Message or NpgsqlException.BaseMessage or is there another way to get the ConstraintName from that I am not aware of?</p>