MaxGekk commented on code in PR #56771: URL: https://github.com/apache/spark/pull/56771#discussion_r3474680226
########## docs/sql-ref-ansi-compliance.md: ########## @@ -257,6 +257,8 @@ At the heart of this conflict resolution is the Type Precedence List which defin \*\*\* For a complex type, the precedence rule applies recursively to its component elements. +The `TIME` type does not promote to any other type. The least common type of `TIME(n)` and `TIME(m)` is `TIME(max(n, m))`. Note that Spark's `TIME` type deviates from the SQL standard in two ways: the default fractional-seconds precision is `6` (the ANSI default is `0`), and `TIME WITH TIME ZONE` is not supported. Review Comment: Good point, thanks. Moved the least-common-type statement (`TIME(n)`/`TIME(m)` -> `TIME(max(n, m))`) into the "Least Common Type Resolution" subsection, next to the analogous decimal rule. The "Type Promotion and Precedence" subsection keeps only the note that TIME does not promote to other types plus the SQL-standard deviations. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
