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

Alasql data type improvement #886

Merged
merged 26 commits into from
Mar 29, 2024
Merged

Alasql data type improvement #886

merged 26 commits into from
Mar 29, 2024

Conversation

drelliche
Copy link
Contributor

@drelliche drelliche commented Jan 30, 2024

This pr changes two things about the data in the alasql tables:

  1. numeric data is now numeric in the following columns:
  • lat, lon, expenses, coverage in the patients table
  • observation_value in observations table
  1. Null values are now undefined instead of the string 'NA'. This means that they no longer appear as NA in the tables, now those entries are blank, but they do actually serve as null values for AVG, MAX, MIN, etc.

Heads up that the second change may impact some of the other SQL modules...

Also, note that zip can't be numeric because they all start with 0 up there in Massachusetts lol

@drelliche drelliche linked an issue Jan 30, 2024 that may be closed by this pull request
@drelliche drelliche marked this pull request as draft January 31, 2024 18:10
drelliche and others added 3 commits February 7, 2024 12:34
* Update data types in alasql tables

Changed numbers to numeric data type from strings.

* Update sql_joins.md

* Revert "Update sql_joins.md"

This reverts commit dce6bd6.

* Increment version number

* Revert change to current version description
@leemc-data-ed
Copy link
Contributor

As far as I can tell, everything in SQL Basics works as expected, and there are no references to NULL values being "NA".

@drelliche drelliche marked this pull request as ready for review March 29, 2024 15:54
@drelliche
Copy link
Contributor Author

@pm0kjp Could you take a look at the SQL intermediate changes? Once you do, we will have to change the macros to point back to main.

@drelliche drelliche requested a review from pm0kjp March 29, 2024 15:56
@pm0kjp
Copy link
Contributor

pm0kjp commented Mar 29, 2024

I made a couple of small suggestions around the quiz. I struggled to understand the second question in the CASE/LIKE quiz so I did reword that, but I'm flexible!

drelliche and others added 4 commits March 29, 2024 13:02
Co-authored-by: Joy Payton <pm0kjp@users.noreply.github.com>
Co-authored-by: Joy Payton <pm0kjp@users.noreply.github.com>
Co-authored-by: Joy Payton <pm0kjp@users.noreply.github.com>
Co-authored-by: Joy Payton <pm0kjp@users.noreply.github.com>
@drelliche
Copy link
Contributor Author

@pm0kjp These were all great suggestions, and I incorporated all of them. I have the change to point the macro back to main as a suggestion, and then I think it is ready to go (until its next revamp)

Co-authored-by: drelliche <99294374+drelliche@users.noreply.github.com>
@pm0kjp
Copy link
Contributor

pm0kjp commented Mar 29, 2024

@drelliche I committed the change to point back to main.

@pm0kjp pm0kjp merged commit e9c62f1 into main Mar 29, 2024
2 checks passed
@pm0kjp pm0kjp deleted the alasql_data_type_improvement branch October 31, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Data type in SQL macro templates
3 participants