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.

Sign up for GitHub

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

Jump to bottom

Better handling of non scalar parameters #32

Open
Lun4m opened this issue Oct 9, 2024 · 1 comment
Open

Better handling of non scalar parameters #32

Lun4m opened this issue Oct 9, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Lun4m
Copy link
Collaborator

Lun4m commented Oct 9, 2024

For now, we treat everything as a string based on if Stinfosys says the parameter is non scalar, we should do some analysis to figure out what the types actually are.
It's also possible that parameters marked as scalar are not floats.
@Lun4m
Copy link
Collaborator Author

Lun4m commented Oct 11, 2024

I did a quick dump of the data types present in KDVH, and indeed, there are many int16, int32, and arbitrary precision numbers (numeric in PostgreSQL).

@Lun4m Lun4m added the enhancement New feature or request label Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lun4m