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

[Bug]: Postgres money type is inferred as categorial input #64

Open
Alexnortung opened this issue Mar 20, 2024 · 1 comment
Open

[Bug]: Postgres money type is inferred as categorial input #64

Alexnortung opened this issue Mar 20, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Alexnortung
Copy link

Short description of current behavior

I am using a postgres database with a money column that has several different values. But mindsdb (or lightwood) infers it as categorial input.

Video or screenshots

When using the sdk I get the following data:

billede

Expected behavior

I would expect the money column to be inferred as a number column, since in postgres it is also a numeric value and is defenitely not a categorial value.

How to reproduce the error

  • Use a posgres database
  • create a table with a money column
  • add several rows with different values
  • create a model for it in mindsdb and see that it is inferred as categorial input

Anything else?

I think part of the problem is that postgres formats the money column output.

@Alexnortung Alexnortung added the bug Something isn't working label Mar 20, 2024
@ZoranPandovski
Copy link
Member

Thanks for reporting this @Alexnortung . It looks like the issue is in our type_infer library. We will check this. @paxcema Should we transfer this issue to type_infer repo ?

@paxcema paxcema transferred this issue from mindsdb/mindsdb Mar 25, 2024
@paxcema paxcema self-assigned this Mar 25, 2024
@paxcema paxcema removed their assignment Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants