-
Notifications
You must be signed in to change notification settings - Fork 285
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
Cannot read property 'getQueryInterface' of undefined #805
Comments
I solved it by downgrading sequelize to 5.21.10 |
Same problem here |
Also solved by downgrading sequelize (this time to |
I was on Sequelize 5.21.13 and upgraded to 6.3.4 and got the same error. Am reverting back to 5.21.13 until this has been fixed. |
Same |
same problem here ): |
same |
Guys please do not reply "same", it does not add anything to the discution. Use the thumb up reaction on the top message if you want to show your interest in the resolution of this issue. |
EDIT: Already fixed in master. While examining the stack trace, the issue is caused because when the However, some are getters which require @RobinBuschmann I think an easy fix is to add
|
to query to our provisioned server to get all the images that has been filtered by users From the previous commit, the endpoint added was to download an image from a public url. We also upload the image to our server through signed url. We set our S3 bucket to be secure from our class note FYI:***** Fixed the last bug from the last commit by upgrading the transpile target to js file from es5 to es6 in the tconfig file from the help from this link sequelize/sequelize#11270 ** sequelize/sequelize-typescript#366 some other error i encountered but was minor Another thing to have in mind was when i download the latest sequelize package of 6.3.5, i get an error when i call the addModels() method. But i solve the issue by following the link sequelize/sequelize-typescript#805 However, you will have to set your compiler to still compile even though it will still show a syntax error at the function argument. Its all good ;)
same |
ts-node version ^9.0.0 The error still persists in version 6.3.5
Should I just downgrade for the time being? |
Version 5.22.3 works fine at the moment.
|
I m getting this error too, is there any to solve this bug without downgrading the version ? |
Yes, I am also get this error. And resolve when downgrading sequelize@5.22.3 version. |
resolved by downgrading to sequelize@5.22.3 |
You can use When using pnpm you can simply do: package.json
It's already fixed in master as mentioned here: #805 (comment) |
@vjpr it also works by installing |
I have this error when using reference in one model and this model starts later (using ModelName.init) |
Issue still persist even with sequelize-typescript@next, or npm:@vjpr/sequelize-typescript@^1.1.0-vjpr.0 |
Hey @russocorp, Can you please elaborate it more? |
What he/she means, I think, is that before running or instanciating a model that has a relationship with other models, make sure its dependents are ran first. In the example below, OrderProduct (which is a pivot table that has references to both order and product) will throw an error
To fix, just change the order. This way, the dependencies of
|
I was able to resolve that by upgrading also packages
|
Yes, that's exactly what happened. |
I don't have any established relationships, and I get this error no matter what version of sequelize I try. 5.22.3, 5.22.1, and any of the 5.21 branches |
I've basically been flopping back and forth between this error and |
This worked for me as well. Thanks |
You might not need to downgrade the package, watch what your passing to the reference field, its supposed to be a reference to another table name, that why you get this error. its a TYPERROR |
ts-node version 8.3.0
typescript version 3.8.3
node nersion 14.4.0
sequelize version 6.2.4
sequelize-typescript version 1.1.0
The text was updated successfully, but these errors were encountered: