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
Describe the bug
I'm receiving an error when trying to call the CartoDB API used by Philly's deeds open records dataset from directly in R files. It appears to be a problem with my local machine's homebrew installation of Postgre and not a problem in the R code itself.
To Reproduce
Steps to reproduce the behavior:
In Kathryn_Hurchla_final_project_RE_LLC_Slidy.Rmd uncomment out the {r PosgreSQL connection} code chunks beginning at line 211; 234.
Highlight and run those code chunks
See error
Expected behavior
The R script runs the SQL query directly through the API and results of data are loaded into the PostgreSQL environment database installed locally on my computer
Screenshots
None available at this time
Desktop (please complete the following information):
OS: iOS Catalina
Browser: Chrome
Version 88.0.4324.96 (Official Build) (x86_64)
Smartphone (please complete the following information):
N/a
Additional context
MacBook Pro 16" 2019; Homebrew installation of PostgreSQL
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm receiving an error when trying to call the CartoDB API used by Philly's deeds open records dataset from directly in R files. It appears to be a problem with my local machine's homebrew installation of Postgre and not a problem in the R code itself.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The R script runs the SQL query directly through the API and results of data are loaded into the PostgreSQL environment database installed locally on my computer
Screenshots
None available at this time
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/a
Additional context
MacBook Pro 16" 2019; Homebrew installation of PostgreSQL
The text was updated successfully, but these errors were encountered: