You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.
Description
When a bit64::integer64 column is provided to fmt_currency(), no formatting occurs, and no warnings are displayed. This is relevant as queries to many databases via the odbc package return integer64 columns when a database column type calls for a large integer (ie Databricks' bigint type).
Hi! Thanks for the report. The reason is that fmt_currency() (and most other fmt_*() functions only work with numeric or integer types. From fmt_currency() docs
fmt_currency() is compatible with body cells that are of the "numeric" or "integer" types. Any other types of body cells are ignored during formatting. This is to say that cells of incompatible data types may be targeted, but there will be no attempt to format them.
You'd likely need to use fmt() to format these.
You can set an option to be on the safe side, but that means you will have to manually specify columns in all your fmt_*() calls.
Prework
Description
When a
bit64::integer64
column is provided tofmt_currency()
, no formatting occurs, and no warnings are displayed. This is relevant as queries to many databases via theodbc
package returninteger64
columns when a database column type calls for a large integer (ie Databricks'bigint
type).Reproducible example
Expected result
Either formatting to work successfully, or a warning displayed that the indicated column cannot be formatted due to a type mismatch.
Session info
The text was updated successfully, but these errors were encountered: