OHDSI / OHDSI/DatabaseConnector

Output to tibble?

Open
#80 10 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
R
Stars
57
Forks
93
Avg merge
10d 12h
Merged PRs (30d)
1

Description

R data frames are pretty horrible, with lots of automatic conversions that break your code if you're not careful (e.g. 1-row data frames become vectors, strings become factors, etc.)

Perhaps querySql should output tibbles instead? Or should we add a querySql.tibble function?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the querySql entry point and review the tibble proposal. Clarify whether the goal is to change querySql's return type or add querySql.tibble; done requires a decided API direction and documented expected behavior for data-frame edge cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.