Add documentation to CAST operator.
#3668
Conversation
|
|
||
| .. code-block:: sql | ||
|
|
||
| CAST(expression AS target_type) |
There was a problem hiding this comment.
To remain consistent with the rest of the doc, you'd want to put a railroad diagram here.
| The value or expression to be converted. | ||
|
|
||
| * :sql:`target_type` | ||
| The target data type. Can be a primitive type (:sql:`INT`, :sql:`LONG`, :sql:`FLOAT`, :sql:`DOUBLE`, :sql:`STRING`, :sql:`BOOLEAN`) or an array type (e.g., :sql:`INTEGER ARRAY`, :sql:`STRING ARRAY`). |
There was a problem hiding this comment.
INT and LONG should be replaced by INTEGER and BIGINT throughout the document
| Boolean Conversions | ||
| ------------------- | ||
|
|
||
| * :sql:`BOOLEAN` ↔ :sql:`INT`: true = 1, false = 0 |
There was a problem hiding this comment.
This is probably a uni-directional arrow, given the fact that the other direction is written the line underneath.
| INSERT INTO data VALUES (1, 'invalid') | ||
|
|
||
| SELECT CAST(str_value AS INTEGER) FROM data WHERE id = 1 | ||
| -- Error: Cannot cast string 'invalid' to :sql:`INT` |
There was a problem hiding this comment.
Is that the actual error message?
I guess the error message should not contain :sql: since this is a RST thing.
There was a problem hiding this comment.
Yeah, the exact error message is: Value out of range for INT. There is something to be said about rewriting error messages originating from the Cascades types system validations and the upper relational layer SQL types., and overall consistency of SQL error messages, as in e.g. #3583.
|
Looks like you had a search replace mishap, can you fix that? |
You're right, I reverted the newly invented type |
2 participants
With #3647 we introduce support for
CASToperator, this adds documentation of this operator, including supported casts, error codes, and degree of compliance to the SQL standard.This fixes #3662.