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

SQL data type error #12651

Closed
radamesbispo opened this issue Jan 16, 2025 · 4 comments · Fixed by #13037
Closed

SQL data type error #12651

radamesbispo opened this issue Jan 16, 2025 · 4 comments · Fixed by #13037
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@radamesbispo
Copy link

Bug Description

the data type is correcly mapped with sql and 100% perfectly in old version of n8n. bug start after update for version 1.75.0

Image

To Reproduce

go to pstgresSql
insert some number to store on it
see the result

Expected behavior

the behaviour expect is save the data

Operating System

ubuntu

n8n Version

1.75.0

Node.js Version

dont know

Database

PostgreSQL

Execution mode

queue

@Joffcom
Copy link
Member

Joffcom commented Jan 16, 2025

Hey @radamesbispo,

We have created an internal ticket to look into this which we will be tracking as "N8N-8130"

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Jan 16, 2025
@Joffcom
Copy link
Member

Joffcom commented Jan 16, 2025

As a possible work around does it work if you try wrapping it in Number() or parseInt()

@radamesbispo
Copy link
Author

the postgresSql are receiving NUMBER, the problem are not in the input but inside of node.... i have try Number() or parseInt() but even do not work

@dana-gill
Copy link
Contributor

@radamesbispo I'm having trouble reproducing the issue. Would you mind sending in workflow to be sure? 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants