How to do initial commit to version control with DataGrip?

I developed a database inside of DataGrip and then bought a license in an attempt to commit to source control. I have installed the GIT plugin and started a new project connected to the postgres database. Now I am unable to do an initial commit to Git. Datagrip insist there are no changes to commit and won't let me even do an initial commit.

What am I missing?

7 comments
Comment actions Permalink

Hi,

What changes do you want to commit?

Do you have any *.sql files to put under version control?

Thank you.

0
Comment actions Permalink

I do not. Up until now I have not been breaking out my database into SQL files and just been designing on the fly. Do I need to personally manage individual files for tables and functions?

0
Comment actions Permalink

Hi,
What do expect to commit?
In general, there are schema creation files, migration scripts and etc. to put under version control.
Thank you.

0
Comment actions Permalink

All of the above. But the part I am worried about is how Datagrip handles VC. It appears that I need to manage all of the files myself? Other database VC's I have used in the past manage files for me based off of the actual schema of the database.

0
Comment actions Permalink

@ Andycooper S Hi,
> It appears that I need to manage all of the files myself?
Yes, you're right.

Could you provide an example for "Other database VC's...".

Thank you.

0
Comment actions Permalink

http://www.red-gate.com/products/sql-development/sql-source-control/ 

 

Red Gate source control is the best DB version control I have used in the past. Where it really comes in hand is if you want to work off a development database and you make changes to stored-procedures, tables and views without having to commit. You can then test and modify and wait until the end of development to find changes and push to source control. All without ever having to touch and track changes to files.

0
Comment actions Permalink

@Andycooper S Hi,

As I mentioned above, you need to manage scripts by yourself.

Thank you.

0

Please sign in to leave a comment.