Комментарии:
Thank you, bro. It was very helpful!
ОтветитьThanks❤, it's working like a charm
ОтветитьThank you so much! I also liked how you figured out the issues in the video without cutting the video
ОтветитьHelp me a lot! Thanks man
Ответитьthx, it's useful af. like it
ОтветитьDude! Thanks a lot seriously! This video must be at Nestjs and Typeform docs!!! Can not believe that I almost lost the day trying to find a way to create my migration
Ответитьdo you why i might get this error:
Error during migration generation:
TypeError
at Reflect.getMetadat
sounds familiar ?
Extremely helpful video. Thanks a lot!
ОтветитьI have been struggling to make it happen. You made my day. 👍
ОтветитьNo amount of words can explain how thankful I am. Umetisha chief...
ОтветитьHey, i am having issues when doing this in a express-ts project without nextjs. I have a src folder which contains ts files and a dist folder which output js files in same name as ts except with .js extension. Everything is working except the migrations commands.
"start": "cross-env NODE_ENV=dev node dist/server.js",
"typeorm": "npm run start && ts-node ./node_modules/typeorm/cli",
"typeorm:generate-migration:win": "npm run typeorm -- -d ./src/api/database/initialize.ts migration:generate ./dist/api/database/migrations/FirstMigration"
The commands run but the migration file doesnot generate. Please help
God bless u sir
ОтветитьThanks
ОтветитьExcellent work
Ответитьcan you share us the repo? thanks
ОтветитьCan you givr us a tutorial for the new seeding please ?
ОтветитьWhy on earth would they change this and not update their documentation? They just say, "Make sure to create a database config file and give it the path" and that's gotta be as vague as humanly possible.
ОтветитьI've spent hours reading nest js and typeorm docs, and finaly found this video. Eveything works perfect, thank you!
ОтветитьEveryone who gets this warning:'No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command' - This is either because you did not have Entity() decorator or because the table already exists in the DB. Remember, in the video, the table was first deleted before the command to run migrations was run
Ответитьplease give me source github bro
Ответитьhow to read database config from env file
ОтветитьI spent three days with the documentation to no avail. I should have gone here first. Thanks!!!
Ответитьthanks! worked well for me.
ОтветитьThank you very much!
In the newer versions of TypeORM, the @EntityRepository() decorator has been deprecated.
any idea how to solve that ?
Very Good Content
ОтветитьThanks!!
ОтветитьEveryone who gets this warning:'No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command', add the @Entity() docorator to your entity class
ОтветитьThanks for the explanation, this perfectly resolve my problem with migrations in the TypeORM.
ОтветитьI have been pulling my hair with the breaking changes from typeorm >= 0.3 versions, I'll update this thread if it comes out successful!
ОтветитьTYVM!
Ответитьwhich vs-code theme are you using? it looks awesome!
Ответить"No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command"
Please tell how to solve this.......... the only difference in my code is that i'm using Postgres and i've used graphql instead of rest
api
Thank you very much, very useful and worked perfectly.
ОтветитьThanks very useful. Also, what about Seeding? Is it the same as of you old tutorial.
Ответить"No changes in database schema were found - cannot generate a migration" issue. Did anyone solve this ? I'm using typeorm 0.3. Thanks
ОтветитьVery Helpful. What is the exact version of typeorm you are using in this video?
ОтветитьThis work for postgresql?
Ответить+1 for the "No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command" error ((
Ответить @Amitav Roy I am getting an error, when i run the migrations. It says there are no migrations to run, even though there are pending scripts in the DB.
Can you please share the repo link for this codebase
Hello sir, can you share a github repo link of this code? because I am getting an error "No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command" or please make a video how to solve this issue
Ответитьnice thanks... please add in the playlist
ОтветитьHow about if i want to use config service for env when creating a datasource?
ОтветитьCrack +10
ОтветитьCan you inject the config service to datasource for env vars? I can only get it working with dotenv package, it'd be nice if there was a workaround by using config service itself
ОтветитьNo changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command.
ОтветитьYou saved me too!!! Thank you so much! You are genius!!! LOL
ОтветитьThis is a great guide.
I spent a lot of time setting up migrations.
like, share, subscribe
Great Video We are facing
No changes in database schema were found - cannot generate a migration. To create a new empty migration use "typeorm migration:create" command