{"id":45749,"date":"2026-11-01T07:00:00","date_gmt":"2026-11-01T07:00:00","guid":{"rendered":"https:\/\/www.withdata.com\/blog\/?p=45749"},"modified":"2026-11-01T08:33:24","modified_gmt":"2026-11-01T08:33:24","slug":"sqldumpsplitter-1-5-released","status":"publish","type":"post","link":"https:\/\/www.withdata.com\/blog\/pr\/sqldumpsplitter-1-5-released.html","title":{"rendered":"SQLDumpSplitter 1.5 Released: GTK3 Linux Build, Honest Exit Codes and a Table Name When You Need One"},"content":{"rendered":"

November 1, 2026 \u2014 Withdata Software announces SQLDumpSplitter 1.5<\/a><\/strong>, the tool that cuts a multi-gigabyte SQL dump into files you can actually restore. This release is mostly the Linux build catching up with the Windows one \u2014 it runs on GTK3 desktops and installs from the apt<\/code> and dnf<\/code> repositories \u2014 plus three things that matter more than they sound: a failed split now says so, splitting by row count no longer writes nothing when you forget the table, and the Linux dialogs stopped overlapping each other.<\/p>\n

\"SQLDumpSplitter<\/p>\n

What\u2019s New in SQLDumpSplitter 1.5<\/h2>\n

1. It Runs on Current Linux Desktops (GTK3)<\/h3>\n

Current Linux desktops ship GTK3 only, while SQLDumpSplitter 1.4 was built against GTK2 \u2014 on those systems it either refused to start or opened with a window whose panels were the wrong size. 1.5 is built with the GTK3 widget set, uses the same fonts and spacing as the Windows build, and is installed from the Withdata apt<\/code> and dnf<\/code> repositories, so an update is sudo apt upgrade<\/code> rather than a download and a copy.<\/p>\n

2. A Failed Split No Longer Looks Like a Successful One<\/h3>\n

A split used to exit with 0 even when it produced nothing \u2014 a source file that is not there, a destination it cannot write to, a dump it cannot parse. In a window that is invisible; in a scheduled task it is worse, because the job reports success and the parts are missing. 1.5 returns a non-zero exit code when the split fails, so a script or a task scheduler can tell the two apart.<\/p>\n

3. Splitting by Row Count Asks for the Table<\/h3>\n

Splitting a dump by rows only makes sense for one table at a time, and the table has to be named. Without a name the run used to finish quietly with no files at all. It now says which table it needs and stops, instead of leaving you with an empty folder.<\/p>\n

4. Cleaner Dialogs on Linux<\/h3>\n

After the move to GTK3 several controls had drifted: the labels on the split pages sat at the wrong offsets, the Max File Size field and its \u201cMB\u201d label overlapped, and the Start-a-task dialog drew its checkbox on top of a button. All of that is laid out properly now, and switching between the split-by pages no longer redraws them.<\/p>\n

About SQLDumpSplitter<\/h2>\n

SQLDumpSplitter<\/a> splits a large SQL dump into smaller files \u2014 by table, by file size, or by row count \u2014 on a desktop machine, without uploading anything.<\/p>\n