-
Notifications
You must be signed in to change notification settings - Fork 190
Case sensitivity when translating to SQL #181
Copy link
Copy link
Closed
Labels
bugan unexpected problem or unintended behavioran unexpected problem or unintended behaviordplyr verbs 🤖Translation of dplyr verbs to SQLTranslation of dplyr verbs to SQLhelp wanted ❤️we'd love your help!we'd love your help!tidy-dev-day 🤓Tidyverse Developer Day rstd.io/tidy-dev-dayTidyverse Developer Day rstd.io/tidy-dev-day
Milestone
Metadata
Metadata
Assignees
Labels
bugan unexpected problem or unintended behavioran unexpected problem or unintended behaviordplyr verbs 🤖Translation of dplyr verbs to SQLTranslation of dplyr verbs to SQLhelp wanted ❤️we'd love your help!we'd love your help!tidy-dev-day 🤓Tidyverse Developer Day rstd.io/tidy-dev-dayTidyverse Developer Day rstd.io/tidy-dev-day
Type
Fields
Give feedbackNo fields configured for issues without a type.
Some SQL functions may be case-sensitive, for instance spatial methods in MSSQL. The syntax is a bit weird, e.g.
colname.STBuffer(1)forSTBuffer(), the callCOLNAME.STBUFFER(1)fails.Created on 2018-11-05 by the reprex package (v0.2.1.9000)
(This example works identically with MSSQL, using SQLite for the reprex.)
What's the reason for converting all function calls to uppercase?