Version control systems can get hung up on large dump files, and opening large dump files to resolve conflicts can be virtually impossible.

One method could be to have an option to break up the database by tables and distribute the dumps amungst multiple files.

Comments

moshe weitzman’s picture

moshe weitzman commented

Yes, I think a dump per table is a decent idea.

ceardach’s picture

ceardach commented
Version: 5.x-1.x-dev » 6.x-2.x-dev
Assigned: Unassigned » ceardach
Status: Active » Fixed

Now dumping per table, and performing merges without any dump or restore. Overall, this should theoretically be tremendously faster on large databases. It will all depend upon the file system and speed of the system performing the merge. Theoretically, a merge on a database several gigabytes large should take roughly 20-40 minutes.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.