Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raise error if data type domain differs between R and database #6

Open
1 of 3 tasks
krlmlr opened this issue Aug 26, 2020 · 2 comments
Open
1 of 3 tasks

Raise error if data type domain differs between R and database #6

krlmlr opened this issue Aug 26, 2020 · 2 comments

Comments

@krlmlr
Copy link
Member

krlmlr commented Aug 26, 2020

It's the only safe way. We might need to make this an option, though, to support legacy user code.

  • Embedded NUL
  • 2⁻³¹ vs. NA
  • Number out of range
@krlmlr
Copy link
Member Author

krlmlr commented Sep 6, 2021

With ALTREP, we can achieve this:

  • fetch the data in a format closer to the database library
  • create R data structures on the fly, as necessary (e.g. postpone string allocation)
  • offer different representations if a conversion into the default format is impossible

@krlmlr
Copy link
Member Author

krlmlr commented Oct 29, 2021

For now, let's convert types in SQL. Maybe in a future rewrite.

@krlmlr krlmlr closed this as completed Oct 29, 2021
@krlmlr krlmlr transferred this issue from r-dbi/RPostgres Oct 31, 2021
@krlmlr krlmlr reopened this Oct 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant