Changed to use the PARAM_INDEX_OUT_OF_BOUND one above instead.


On 2/11/13 5:56 PM, "James Taylor" <notifications@github.com> wrote:

In src/main/java/com/salesforce/phoenix/exception/SQLExceptionCodeEnum.java:
> +    RESULTSET_CLOSED("XCL01", "ResultSet is closed."),
> +    GET_TABLE_REGIONS_FAIL("XCL02", "Cannot get all table regions"),
> +    EXECUTE_QUERY_NOT_APPLICABLE("XCL03", "executeQuery may not be used."),
> +    EXECUTE_UPDATE_NOT_APPLICABLE("XCL03", "executeUpdate may not be used."),
> +    SPLIT_POINT_NOT_CONSTANT("XCL04", "Split points must be constants."),
> +
> +    /**
> +     * Implementation defined class. Phoenix internal error. (INT).
> +     */
> +    INTERNAL_ERROR("INT00", "Internal error."), // General error, should have a message for details.
> +    CANNOT_CALL_METHOD_ON_TYPE("INT01", "Cannot call method on the argument type."),
> +    MALFORMED_URL("INT02", "Malformed URL."),
> +    CLASS_NOT_UNWRAPPABLE("INT03", "Class not unwrappable"),
> +    PARAM_INDEX_OUT_OF_BOUND("INT04", "Parameter position is out of range."),
> +    BIND_INDEX_OUT_OF_BOUND("INT04", "Index of bind out of bounds."),
> +    PARAM_VALUE_UNBOUND("INT05", "Parameter value unbound"),
Minor, but can you name this BIND_VALUE_UNBOUND so that it matches the terminology used in the above one too (or use PARAM in the other one - either way, but just so they're consistent)


-
 Reply to this email directly or view it on GitHub <https://github.com/forcedotcom/phoenix/pull/35/files#r2972523> .