-
-
Notifications
You must be signed in to change notification settings - Fork 860
[BUG]: Column name conversion not working when using sql.js
#3642
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
Open
1 task done
Comments
Incidentally, I believe I have identified the source of the issue. drizzle-orm/drizzle-orm/src/sql-js/session.ts Lines 42 to 70 in 599da5e
It is evident that the I am passionate to open a new Pull Request to fix this issue. |
rockmagma02
added a commit
to rockmagma02/drizzle-orm
that referenced
this issue
Nov 28, 2024
rockmagma02
added a commit
to rockmagma02/drizzle-orm
that referenced
this issue
Nov 28, 2024
rockmagma02
added a commit
to rockmagma02/drizzle-orm
that referenced
this issue
Nov 28, 2024
rockmagma02
added a commit
to rockmagma02/drizzle-orm
that referenced
this issue
Nov 28, 2024
rockmagma02
added a commit
to rockmagma02/drizzle-orm
that referenced
this issue
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report hasn't been filed before.
What version of
drizzle-orm
are you using?0.36.4
What version of
drizzle-kit
are you using?0.28.1
Other packages
No response
Describe the Bug
Column name conversion not working when using
sql.js
Description
Here is a simple example can show this bug:
As you can observe, the table contains a column named
test_snake_name
. We utilize thetestSnakeName
to refer to this column in the Drizzle schema. However, there is an issue:The query was successfully executed, and the result was retrieved. However, the retrieved data was not converted to the appropriate object type suitable for use in TypeScript or JavaScript code. Instead, it retains the name stored in the database.
Other info
I discovered similar (or identical) issues in #2189, which was opened on April 22, 2024. However, due to the high volume of issues, it appears that your team may have overlooked this matter. Therefore, I am re-reporting it here for your attention.
The text was updated successfully, but these errors were encountered: