You are welcome! In general, you would want to write the database as code, but there are too many choices to mention. Of course the very popular method, even today, is to create stored procedures and SQL scripts. You can then create a shell script that takes in options like a server name, port, etc and then the script builds the database for you. More modern document DB’s aren’t much more than the variables you write in code that are then translated to JSON.
Hi so if someone wants to clone my project and work on it and then push it again when I pull the changes will be on my project? I mean I'm trying to find a way to work with my team and have the same db everything there is change so everyone is on the same page. Will this work ? I hope I made myself clear.....
There are two ways you can go about this. You can have everyone clone and then send PRs. If you accept, then they will need to pull those changes from your source. That sounds complicated if you always want everyone to be in the same place. What you might do instead is to add people you trust to your repo. Anytime they create a change, they create a new branch and do a PR from there. Once complete, you merge that to `main` and then everyone just creates new branches from that all over again. If one team member needs changes from one another or from main, they can do a `git-merge` or a `git cherry-pick`
@@bill-raymond yes I we've got the the branch and the pull requests but we can't figure out what to do with the database.... so everyone has the same one and if there is a change in the db everyone's will still have the same.... we are trying to do it with a local db without sql server but we can't figure out how .... thank you so much for answering bc I'm out of ideas.......
@@georgiarammou1357 I must not have been paying close attention to your question, so I apologize. It all depends on what kind of database you are creating. One option of course is to write SQL Scripts that create and or modify databases as you go. That can get a little unwieldy with lots of people working on it. Another option is to create a `main` database that every syncs to using any number of tools. I heard this is popular: github.com/leapfrogtechnology/sync-db. And of course yet another way is to build the data model in code that can output the final database. I think it all depends on the db technology you are using, the size of the team, the programming language you are using, etc. If you can specify more details, I may be able to help or at least point you in a direction
This works with any codebase and is using a standard feature of Git (and therefore GitHub). Do keep in mind, storing a full database in your application is not necessarily a good idea in practice. That said, some people do need that functionality, so I provide it as an example.
![Summer Walker - Heart Of A Woman [Official Lyric Video]](http://i.ytimg.com/vi/SFddctbZzw8/mqdefault.jpg)
Year 2024, your save me.
I am glad this video helped you!
Thanks for the video! Instead of uploading the db, how do you upload the script of the database as you suggested ?
You are welcome! In general, you would want to write the database as code, but there are too many choices to mention. Of course the very popular method, even today, is to create stored procedures and SQL scripts. You can then create a shell script that takes in options like a server name, port, etc and then the script builds the database for you. More modern document DB’s aren’t much more than the variables you write in code that are then translated to JSON.
Hi so if someone wants to clone my project and work on it and then push it again when I pull the changes will be on my project? I mean I'm trying to find a way to work with my team and have the same db everything there is change so everyone is on the same page. Will this work ? I hope I made myself clear.....
There are two ways you can go about this. You can have everyone clone and then send PRs. If you accept, then they will need to pull those changes from your source. That sounds complicated if you always want everyone to be in the same place. What you might do instead is to add people you trust to your repo. Anytime they create a change, they create a new branch and do a PR from there. Once complete, you merge that to `main` and then everyone just creates new branches from that all over again. If one team member needs changes from one another or from main, they can do a `git-merge` or a `git cherry-pick`
@@bill-raymond yes I we've got the the branch and the pull requests but we can't figure out what to do with the database.... so everyone has the same one and if there is a change in the db everyone's will still have the same.... we are trying to do it with a local db without sql server but we can't figure out how ....
thank you so much for answering bc I'm out of ideas.......
@@georgiarammou1357 I must not have been paying close attention to your question, so I apologize. It all depends on what kind of database you are creating. One option of course is to write SQL Scripts that create and or modify databases as you go. That can get a little unwieldy with lots of people working on it. Another option is to create a `main` database that every syncs to using any number of tools. I heard this is popular: github.com/leapfrogtechnology/sync-db. And of course yet another way is to build the data model in code that can output the final database. I think it all depends on the db technology you are using, the size of the team, the programming language you are using, etc. If you can specify more details, I may be able to help or at least point you in a direction
@@bill-raymond can I contact you somewhere else bc I think yt deletes my other comments
@@georgiarammou1357 calendly.com/billraymond/30min
you saved me. Thank you
Great! You are very welcome!
I don’t have App data folder... Why?
You need to create a _data folder. It is not always created for you
@@bill-raymond thanks for help❤️
No problem!
Does this work with asp.net core, web application (Non MVC)?
This works with any codebase and is using a standard feature of Git (and therefore GitHub). Do keep in mind, storing a full database in your application is not necessarily a good idea in practice. That said, some people do need that functionality, so I provide it as an example.
@@bill-raymond thank you!!
You’re welcome!
You are the best a great!! Teacher @Bill Raymond
Essam Khattab glad I could help!
@@bill-raymond keep up!!!