DataPeach
A fast, light database client for Windows and Linux.
SQL consoles saved as files, tables you can browse and edit, and every change reviewed as SQL before it reaches the database.
›_ posts-this-week.sql
-- Posts published since a date
SELECT p.id, p.title, u.name
FROM posts p
JOIN users u ON u.id = p.author_id
WHERE p.published_at > :since
ORDER BY p.published_at DESC;Staging · 3 pending changes
~ UPDATE posts SET title = 'Hello world'
WHERE id = 42;
+ INSERT INTO tags (name) VALUES ('sql');
− DELETE FROM drafts WHERE id = 7;Why DataPeach
The everyday work, with just what it needs
Full database clients are heavy (a JVM, hundreds of MB, seconds to open) or paid. DataPeach opens in ~240 ms, uses ~30 MB idle and writes nothing to the database without you seeing it first.
Fast
The grid only draws what you see: 50,000 rows cost the same as 50, and the first ones show up while the query is still arriving.
Nothing reaches the database unseen
Editing cells, adding or deleting rows writes nothing: the changes wait in staging as SQL and are applied together in one transaction.
Care per connection
Mark a connection as production (everything that writes asks first) or read-only (nothing that writes runs).
Consoles are files
Every console is a
.sqlfile saved as you type. With a project folder they go to.peach/queries/, ready to version with git.
How it works
Editing is not writing
Grid edits pile up as SQL in a separate panel. You review them, undo what you did not mean and apply everything together, or nothing.
Staging
Several edits to a row are merged into one UPDATE, and rows are identified by their primary key. Apply (Ctrl+Shift+K) runs everything in one transaction: if something fails (a foreign key, a row someone else deleted), nothing is applied and the changes stay pending.
- ~Edited cell
- +New row
- −Row to delete
Two modes per connection
Keyboard
Shortcuts
They are all listed in About (F1). The common ones are the same in every Peach app.
General
| Ctrl+P | Go to table / open connection |
| Ctrl+Shift+O | Open connection (quick search) |
| Ctrl+Tab / Ctrl+Shift+Tab | Next / previous tab |
| Ctrl+W | Close console or table |
| F1 | About, shortcuts and language |
| F5 | Read the structure again |
Queries and data
| Ctrl+Enter / Ctrl+Shift+Enter | Run the statement / the whole console |
| Esc | Cancel the query |
| Ctrl+Space | Complete |
| Ctrl+N | New console |
| F4 | Open the table's data |
| Ctrl+Shift+K | Apply pending changes |
The Peach family
Works better with its siblings
GitPeach
gitpeach.peachapps.org
A plain, transparent git client for Windows and Linux.
Consoles live in your project's .peach/queries/: GitPeach versions them along with the code.
Explore GitPeach →
TextPeach
textpeach.peachapps.org
A code viewer and analyzer, read-only by design.
TextPeach reads the queries in your repository, with their outline and git status, with no fear of touching them.
Explore TextPeach →
RestPeach
restpeach.peachapps.org
A local, git-native API client.
RestPeach tests the API; DataPeach shows what it left in the database. Both keep their work in your repository.
Explore RestPeach →
A single portable .exe
No installer and no .NET to install. With a
portable.txtnext to it, data is stored beside the executable.No accounts or telemetry
No sign-up, no sync and no automatic updates. Nothing leaves your machine unless you ask for it.
Your files, your repository
Everything lives in folders and text files you already track with git. No hidden databases.
One family
Same colors, shortcuts and tone. They find each other: a click on the branch opens GitPeach, a button opens TextPeach.
English and Spanish
They follow the system language or the one you pick in About (F1).
Free software
GPL-3.0-or-later. Use them for free, at work too; study the code and share your version.
Download
Nothing reaches the database without being seen first.
Download the executable, put it in any folder and open it. There is no installer and no account to create.