Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Database version control

Javi88's profile image Javi88 posted 1 month ago in Feature discussion Permalink

Hello

First of all, sorry for my bad English (google translate).

I would like to propose an improvement to development. I have tried to make your job easier, doing it myself, but I have Delphi XE and I cannot compile your project.

The idea is: Every time something related to the structure of the database is created / modified / deleted: table, trigger, view, etc., even the database itself. In addition to modifying the database, a copy is also made in a file. In this way you can record the changes that are made in the database with a version control program.

The changes in the user interface are those that I show in the attached image.

The directory structure that the program should create is also attached. The philosophy of the "__history" directory is to copy the previous versions of each modification that was made into it.

Particularly, this addition is very interesting, because finally there will be a possibility to do a version control of a database.

Thank you very much for your time and I hope you like this improvement.

a greeting Javier

2 attachment(s):
  • Interface
  • Directory-structure
ansgar's profile image ansgar posted 1 month ago Permalink

Could it be you crossposted this in issue #985?

However, the idea is indeed nice. There is already a logging feature, which can record everything to a file per session.

For a real-world version control, I doubt this can ever be reliable, as many other clients may also modify the database, as well as an application which was written for the database.

Javi88's profile image Javi88 posted 1 month ago Permalink

Hi.

Issue # 985 is not the same. I say an exclusive file for each one of the tables, views, function, event ... that the database has.

The idea is to save the modifications only from the windows for this purpose. Without using sentences (SQL) written by oneself.

Yes there is discipline, yes. Both for individual projects and collective projects. If everyone makes the changes this way, control is assured. If someone makes a change using another program, they will have to manually upload the change to version control.

Thank you

2 attachment(s):
  • Save
  • files
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
Javi88's profile image Javi88 posted 1 month ago Permalink

Version controls are effective, if users do their job well.

Javi88's profile image Javi88 posted 3 days ago Permalink

Hello ansgar

I have made the improvement. Would you mind reviewing it and if you see fit, add it to your code. Thank you.

I only attach the modified files. Your code is updated to 2020-05-25. I don't know if this is the way to pass the code. It is the first time I do something like this. If it is not the way, please let me know. Thank you.

Regards Javi

Javi88's profile image Javi88 posted 3 days ago Permalink

Sorry, I thought I could attach a zip. Please can you tell me how I can send you the improvement. Thank you.

Please login to leave a reply, or register at first.