Buy

Databases

Free & Premium

On the Databases page you manage the database servers WebDonkey runs on your Mac: MySQL, MariaDB, PostgreSQL and, once installed, MongoDB. For each server you create databases and users, grant privileges, back up a database to a file and restore it. At the bottom of the page sits the DB browser for looking into the tables: Adminer or, with Premium, the WebDonkey view.

Each server has its own data directory in WebDonkey's sandbox. WebDonkey never touches databases of other installations on your Mac, such as Postgres.app or Docker.

What you do here

Page layout

Area Content
Server bar One button per server: MySQL, MariaDB, PostgreSQL and MongoDB when it is installed. A green dot means the server is running. A click shows its card below.
Server card Title with server, version and port (for example “MySQL 8.4.6 · Port 3306”), the data directory below it. On the right the version picker (with several installed versions), the status running, DB browser and Stop, or Start for a stopped server.
Adminer opens with Two pickers for the database and the user the DB browser starts with.
Databases and users The switch Databases (n) and Users (n), next to it the size of all databases on the server, and on the right New database or New user. The list below.
DB browser At the bottom the DB browser (Adminer) card. With Premium you switch between Adminer and WebDonkey view in its header.

While a server is not running, its card only says “Start the server to manage databases and users.” WebDonkey reads the database list and the users straight from the running server.

Default accounts

WebDonkey itself logs in with these accounts:

Server Port Account
MySQL 3306 root, password root
MariaDB 3307 root without a password
PostgreSQL 5432 postgres, password postgres. The local server does not check passwords.
MongoDB 27017 no login, reachable from this Mac only

All servers only accept connections from this Mac. For a site, create a user of its own with privileges on its database only, see Manage users.

Free and Premium

Managing servers, databases, users and privileges, plus backup and restore, is included in Free. The DB browser inside the app, meaning embedded Adminer and the WebDonkey view, comes with Premium. On Free you open Adminer in your browser with Open in browser.

Servers and databases Free

The server card is the heart of the Databases page. Here you start and stop a database server, pick its version and create, rename or delete databases. Every database shows how much disk space it uses.

Where to find it

Sidebar Local › Databases. Pick the server in the server bar at the top, for example MySQL. On the command line, wd db list shows all servers with version, port, status and databases. More in Databases in the CLI.

Start and stop a server

  • Start starts the selected server. While it comes up, it says “Starting …”.
  • Stop stops it. Sites using its databases lose their connection.

WebDonkey asks the server itself whether it is running instead of trusting a leftover socket file. A server that already runs shows as running, a crashed one does not. If a server is not installed yet, install it on the Services page. If its port is taken, a note at the top of the window says so and lets you free the port.

Pick a version

If several versions of MySQL, MariaDB or PostgreSQL are installed, the card shows a version picker on the right. Only one server runs per port, so the choice applies from the next start.

  1. Pick the version in the list.
  2. If the old one is still running, a note tells you which version is running and what the switch means for the data.
  3. Click Restart now. The server starts in the chosen version.
Server What happens to the data
MySQL, MariaDB Each release series (for example 8.0 and 8.4) has its own databases and users. After the switch you see those of the new version. Those of the old one are kept and come back as soon as you switch back. Within a series, databases and users stay the same.
PostgreSQL There is a single data directory, and another major version cannot open it. On start, WebDonkey offers to set the current data aside. Nothing is deleted, the new version starts empty.

The chosen version is the same setting as on the Services page. More in Autostart and lifecycle.

Create a database

  1. Leave the switch on Databases and click New database.
  2. Enter the name of the database under Name, for example shop.
  3. Optional: tick Also create a user for this database. It is a shortcut for a new user with all privileges on this database only. The User and Password fields are already filled with a name and a generated password.
  4. Click Create database or Create database and user.

With a user, WebDonkey finishes with Database and user created, listing server, database, user, password and a connection URL. You see the password only this once.

Server Character set of the new database
MySQL, MariaDB utf8mb4 with the collation utf8mb4_unicode_ci
PostgreSQL UTF-8, owned by postgres

Rules for the name: no spaces at the start or end, at most 64 characters on MySQL and MariaDB, 63 bytes on PostgreSQL, and not the name of a system database. On the Mac, MySQL and MariaDB ignore case, so Shop and shop count as the same name there. If the name exists, WebDonkey says: “A database with this name already exists.”

The database list

Each database is a row with:

  • its name and, if a site uses it, a chip with the site's domain,
  • its size (data and indexes) on MySQL, MariaDB and PostgreSQL,
  • the users with access and their level (see Who may do what),
  • the buttons Access and Backup, the circular arrow for restoring, the pencil for renaming on PostgreSQL, and the trash can for deleting.

Next to the switch you see the total of all databases on the server with the words in total. The system databases (mysql, information_schema, performance_schema, sys on MySQL and MariaDB, postgres, template0, template1 on PostgreSQL) sit collapsed under System databases (n). They belong to the server and cannot be changed or deleted here.

Rename

Renaming only works on PostgreSQL. MySQL and MariaDB cannot rename databases.

  1. Click the pencil in the row (Rename).
  2. Enter the name under New name and confirm.

Data and access rights stay as they are. Nobody may be connected to the database while it is renamed. If a site uses the database, the dialog names it: it needs the new name in its configuration afterwards.

Delete

  1. Click the trash can in the row (Delete database). Delete database? opens.
  2. WebDonkey checks the content first and shows “Tables in this database: n” or “The database is empty.” If a site uses the database, the dialog names it.
  3. If it is not empty, type its name to confirm.
  4. Click Delete for good.

An empty database is deleted without typing. Deleting cannot be undone. Back the database up first if you are unsure.

MongoDB

MongoDB appears in the server bar as soon as it is installed on your Mac. You list, create and delete its databases here too. There are no users and privileges, because MongoDB runs locally without login and only accepts connections from this Mac. Backup and restore on this page are not available for MongoDB, and Adminer does not support it. To work with it, use mongosh or a program like MongoDB Compass with mongodb://127.0.0.1:27017/<database>.

Troubleshooting

What you see Why What to do
“Someone is connected to the database right now” Adminer, the editor or a site holds a connection Close Adminer, the editor and the site that uses it, then try again.
“This server cannot rename databases.” MySQL and MariaDB cannot do that Create a new database, restore a backup of the old one into it, and delete the old one.
“The database server isn't running.” The server was stopped in the meantime Click Start.
The databases of another version are missing On MySQL and MariaDB each release series has its own data Pick the other version and restart. A note in the card names the versions with data of their own.

See also

Backup and restore Free

On the Databases page you back up any MySQL, MariaDB or PostgreSQL database to a file on your Mac, and you restore such a file there as well. It is the quick way before an update or an experiment: one click, one dump, done. Both are included in Free. For regular backups of whole projects including folders, use Backups.

Where to find it

Sidebar Local › Databases, pick the server, then in the database's row Backup or the circular arrow next to it (Restore this database from a backup file). Both buttons are there while the server runs. On the command line, wd db backup and wd db restore do the same. More in Databases in the CLI.

Back up a database

  1. Click Backup in the database's row. Back up database opens.
  2. Pick the Format (see the table). The default is SQL (gzip).
  3. Check the File name. It is a pattern with placeholders, prefilled with {name}_{date}_{time}. File: shows what the file would be called right now.
  4. Check Save to. The default is WebDonkey's backup folder.
  5. Click Create backup. While it runs, the dialog shows the progress, Cancel stops it.
  6. Afterwards it says Backup created with the size and the path. Show in Finder shows the file.

Formats

Format File What for
SQL (gzip) .sql.gz Complete dump, compressed. Can be restored here.
SQL .sql Complete dump as plain text, readable in any editor, restorable.
PostgreSQL archive .dump PostgreSQL only: pg_dump's own format, compressed. Restorable here or with pg_restore.
CSV .zip One CSV file per table, packed as ZIP. For further processing, not for restoring.
JSON .json All tables in one JSON document. For further processing, not for restoring.

File name and folder

Below the File name field you insert placeholders at the cursor with one click:

Button Placeholder Becomes
+ Database {name} name of the database
+ Server {server} MySQL, MariaDB or PostgreSQL
+ Date {date} date like 2026-11-06
+ Time {time} time like 14-30-05

Default name brings back the default pattern. WebDonkey adds the file ending itself, matching the format.

Under Save to, Choose folder… picks another folder, for example on an external drive. Back to the default folder switches back to WebDonkey's backup folder. Nothing is overwritten: if a name is taken, WebDonkey appends -2, -3 and so on. WebDonkey remembers format, pattern and folder for each database, so next time they are already set.

Restore a database

  1. Click the circular arrow in the database's row. Restore database opens.
  2. Read the note A restore overwrites data: the tables in the file replace the current ones in the target database.
  3. Under A file (.sql, .sql.gz, .dump), pick the backup file with Choose…. A .dump file only works with PostgreSQL.
  4. Back up the target database first tells you where WebDonkey puts an SQL backup of the current state beforehand. WebDonkey always takes this backup, you cannot turn it off. So every restore can be undone.
  5. Click Restore…. The confirmation names the database and the file.
  6. Type the name of the target database into the field and click Overwrite. The button only unlocks when the name matches exactly.
  7. At the end the dialog says Restore finished.

Check the result afterwards, for example in the DB browser, and keep the backup from step 4 until you are sure.

What WebDonkey checks before restoring

  • Another database in the file: if the file switches databases itself (USE), creates one or drops one, WebDonkey refuses it and restores nothing. Otherwise it could change a database other than the target. Use a dump of just this one database instead.
  • Another server version: if the file comes from a server with a different version, WebDonkey asks Restore into another version?. Across versions, the result may differ (data types, defaults, functions). Restore anyway goes ahead.
  • Foreign DEFINER: if views, routines, triggers or events in the file run as an account that does not exist locally, WebDonkey asks Rewrite DEFINER?. Rewritten, they run as the account WebDonkey restores with. The file itself stays unchanged. Without rewriting, the restore would stop at the first of these objects.
  • System databases cannot be restored.

What happens in the background

  • WebDonkey's backup folder lives in the sandbox under project-backups/databases/<server>, so by default ~/Library/Application Support/WebDonkey/project-backups/databases/mysql for MySQL.
  • The backup taken before every restore lands there too.
  • A folder of your own must exist. WebDonkey does not create a drive that is not plugged in.

Troubleshooting

What you see Why What to do
No Backup in the row The server is not running, or it is MongoDB Start the server. Back up MongoDB with mongodump.
The file is refused because it switches databases The dump contains USE, CREATE DATABASE or DROP DATABASE Create the dump without --databases (mysqldump) or without -C (pg_dump).
A CSV or JSON file cannot be picked These formats are exports, not backups Use an SQL or PostgreSQL archive file.
“Cancelled. Nothing was restored.” You cancelled before anything was restored Start the restore again.

See also

Manage users Free

Ideally every site gets a database user of its own that may only access its database. The Users view of the server card lists all users of the server with their databases and privileges, and you create new users, set passwords and delete users there. The view exists for MySQL, MariaDB and PostgreSQL.

Where to find it

Sidebar Local › Databases, pick the server, set the switch in the card to Users (n). The number counts your own users, without the server's own accounts. On the command line there is wd db users. More in Databases in the CLI.

Create a user

  1. Click New user.
  2. Enter the name under Name. A note in red means the name is taken, too long, belongs to the server itself or has spaces at the start or end.
  3. The Password is already generated. The buttons at the field generate a new one (Generate a new password), show it (Show) or copy it (Copy). You can also type your own.
  4. MySQL and MariaDB only: under May log in from, choose where the user may log in from.
  5. Optional: pick a database right away under Access to database and the Privileges below it. None, assign later creates the user without a database.
  6. Click Create user.

The final dialog User created lists Server, User, Password, the Database if any, and a ready Connection URL, each with a copy button. You see the password only this once. Put it into your site's configuration, for example .env.local or wp-config.php, and close with Done.

May log in from

Choice Meaning
This Mac only (localhost) Default. Right for every local site.
Any host (%) The user may log in from anywhere.
A specific host … A field for a host name, an IP address or a pattern with % and _.

The server itself still only accepts connections from this Mac (bind-address 127.0.0.1). An account for other hosts only takes effect once you open that in the server's configuration, see Edit configuration files. PostgreSQL has no host per user, pg_hba.conf handles that there. So on PostgreSQL the choice is fixed to this Mac.

With This Mac only (localhost), a MySQL or MariaDB user gets two entries: localhost for connections through the socket and 127.0.0.1 for connections over TCP. That way PHP sites, Adminer and programs like Sequel Ace or TablePlus connect without an extra step.

The user list

Each user is a row with its name, its host entries, the sites that log in with it according to their configuration, and below that its databases with their level. Badges after the name:

Badge Meaning
Admin account WebDonkey manages the server with this account (root, postgres). It cannot be changed or deleted here.
System An internal account of the server.
Superuser May do anything on the whole server.
no login The account cannot log in (on PostgreSQL a role without login).
only via localhost or only via 127.0.0.1 On MySQL and MariaDB one of the two host entries is missing. The server refuses logins the other way.

The server's internal accounts, such as mysql.sys, sit collapsed under Internal server accounts (n).

If an account lacks a host entry, WebDonkey adds it as soon as you assign the user a database or change its password. If the badge is still there afterwards, set a new password.

Assign a database

Click Database in the user's row. Another database for <user> opens: pick the database and the Privileges and click Give access. More on the levels in Who may do what.

Change a password

  1. Click Password in the row.
  2. In New password for <user> a new password is already generated. Keep it or type your own.
  3. Click Set password.

Password changed shows user and password. Below that, WebDonkey names the sites that log in with this user according to their configuration and now need the new password. If there are none, it says: “According to their configuration, no WebDonkey site logs in with this user.”

Delete a user

Click the trash can in the row (Delete user) and confirm Delete user?. The user is removed for good and its grants are lost. If a site logs in with it, the dialog warns you first. On PostgreSQL, tables owned by the user are handed to postgres, the data stays.

PostgreSQL and passwords

The local PostgreSQL server does not ask for passwords (method trust). The view says so in a note. Passwords you set still apply once the database moves to another server. So set them the way the site will need them live.

Troubleshooting

What you see What to do
“This user already exists. Choose “Existing user” or another name.” Give the existing user the database through Database, or pick another name.
“The database server's own accounts (root, postgres and the internal ones) can't be changed here.” Create a user of your own for your site.
“Not a valid host.” Use a host name, an IP address or a pattern with % and _.
The site reports “Access denied” Check user and password in the site's configuration. If the user shows only via localhost, set a new password.

See also

Who may do what Free

The server card shows which user may access which database and with which privileges. WebDonkey reads this straight from the server and keeps no list of its own. So whatever you change here changes the real grants, and whatever someone granted with SQL shows up here as well.

Where to find it

Sidebar Local › Databases, pick the server. The switch in the card offers two views of the same grants:

  • Databases (n): every database with the users who may access it, each with its level. Accounts like root that get into every database anyway appear once above the list: “Every database, no grant needed: root”.
  • Users (n): every user with their databases.

The levels

Level Meaning
All privileges May do anything in this database, including creating, changing and dropping tables.
Read & write May read and change data, but not create or drop tables.
Read only May only read and export.
Custom The privileges were granted by hand. The tooltip lists them.
Owner PostgreSQL only: the user owns the database.

You can grant the first three. Custom and Owner are only shown.

Give access

  1. Click Access in the database's row. Give access opens.
  2. The Database is preselected.
  3. Choose Existing user and the User, or New user. For a new user, WebDonkey suggests a name derived from the database name and a generated Password.
  4. Choose the Privileges. The default is All privileges.
  5. Click Give access or Create user.

If a database has no user of its own yet, its row says “No user of its own yet.” with the link Give access.

Change the level and revoke access

  • Change the level: grant the same user the same database again. The dialog says “<user> already has <level> here. The new choice replaces it.” The new level replaces the old one, downwards too.
  • Revoke: click the × at the user in the database's row (Revoke access) and confirm with Revoke. The user itself stays, only the access to this database goes.

You cannot revoke the access of a PostgreSQL database's owner or of accounts that get into every database anyway.

Sites in the list

A chip with a domain shows which of your sites uses a database or a user. The tooltip names the site and the file in which WebDonkey found it. WebDonkey reads the site's configuration for this (.env, .env.local, wp-config.php and the settings of Drupal and TYPO3) and changes nothing there, passwords included. Before you revoke a site's access, delete its user or delete its database, WebDonkey warns you.

Special grants

The card also shows privileges that did not come from WebDonkey:

Badge Meaning
via <pattern> The access comes from a wildcard grant such as shop% that covers several databases. It can only be changed with SQL, for example in Adminer.
tables only (n) The user has privileges on single tables only. The tooltip names them.
deleted The database is gone, the grant is not. If someone creates a database with this name again, the user has access right away.

If there are grants on deleted databases, a note above the list offers Clean up. After you confirm, WebDonkey removes exactly those grants. Users and their other privileges stay, so do wildcard grants such as shop%.

On PostgreSQL every user may connect to every database, a note above the list says so. What they may read or change inside is shown by the level.

Troubleshooting

What you see Why
“Couldn't read the permissions, so you only see the names.” The server refused the query for the grants. The reason follows.
“System databases can't be granted.” System databases belong to the server.
“This user gets into every database anyway. That can't be revoked for a single one.” The account has privileges on all databases.
“The access comes from the grant … Change it with SQL, for example in Adminer.” The wildcard grant covers several databases.

See also

DB browser (Adminer) Free & Premium

The DB browser is how you look into your databases: browse tables, run queries, edit data, import and export. WebDonkey ships Adminer for this, a lean browser-based database tool that handles MySQL, MariaDB and PostgreSQL. With Premium, Adminer runs embedded at the bottom of the Databases page. On Free you open it in your browser. With Premium you can also use the WebDonkey view instead of Adminer.

Where to find it

  • Sidebar Local › Databases, the DB browser (Adminer) card at the bottom.
  • The DB browser button in the server card.
  • ⌘K and the command Open Adminer: opens the page and starts Adminer in the card.

One-time setup

Adminer is a PHP script. Before you open it for the first time:

  1. Install a PHP version if there is none yet (on the Services page, under the web servers).
  2. Install Adminer on the Services page with Versions in its row (see Install and choose versions).

You don't need to start Adminer yourself. WebDonkey starts it when you open it and it is not running.

How to do it

  1. Pick the server at the top, for example MySQL, and start it if it is not running.
  2. In the server card, choose under Adminer opens with which database and user Adminer starts with. all databases opens the server overview.
  3. In the DB browser (Adminer) card, click Open DB browser. The page scrolls to the card and Adminer shows its login form.
  4. Server, port, user and database are filled in. Enter the password and log in.

You type the password into Adminer itself. WebDonkey never sees or stores it.

Fields and buttons

Element What it does
Adminer opens with Two pickers: the database (all databases or a specific one) and the user. The server's internal accounts are not listed. WebDonkey remembers the choice per server, across app restarts too. If Adminer is open, it reloads with the new choice right away.
Open DB browser The big button in the empty card. Starts Adminer if needed and loads the login for the selected server.
Circular arrow (Reload) Reloads Adminer, for example when it hangs. If it is no longer running, WebDonkey starts it first.
Arrow out of a box (Open externally) Opens the same login in your browser. If Adminer is not running, WebDonkey starts it first.
DB browser in the server card Opens the database the way Settings › Open with › Databases says (see below).

If you switch the server at the top while Adminer is open, Adminer follows. Its look follows your app theme, light or dark.

The DB browser button and Open with

The DB browser button in the server card follows Settings › Open with › Databases:

Setting What happens
Automatic If the WebDonkey Editor is installed, WebDonkey asks Open database: Adminer in WebDonkey or WebDonkey Editor. With Remember my choice it does not ask again. Without the editor, Adminer opens right away.
WebDonkey (Adminer) Always Adminer here on the page.
WebDonkey Editor The editor's database window, right at this server and the chosen database.

More in Open with and the WebDonkey Editor. If the WebDonkey view is selected below, the button jumps to it instead of starting Adminer. The big Open DB browser button in the card always opens Adminer.

What happens in the background

  • Adminer runs as a service of its own on this Mac at http://localhost:8085/, reachable from this Mac only. It uses WebDonkey's PHP version and the shared php.ini.
  • Adminer connects through 127.0.0.1 and the server's port, not through localhost. That is why a MySQL user needs the host entry 127.0.0.1, see Manage users.
  • If you stop Adminer, for example on the Services page, and come back later, the card closes and says: “Adminer is stopped. A click starts it again.”

Free and Premium

Adminer embedded in the app is Premium. On Free you start Adminer the same way with Open DB browser. The card then shows the note Embedded database view is Premium with the Open in browser button, which opens Adminer in your browser with the same prefilled login.

Troubleshooting

What you see What to do
“Adminer is not installed. Install a version with the Versions button in its row.” Click Go to Services and install Adminer.
“Adminer is a PHP script, and no PHP is installed.” Install a PHP version under the web servers and open Adminer again.
Login fails Check user and password. The default accounts are listed under Databases. On MySQL and MariaDB the user needs the entry 127.0.0.1.
No DB browser in the server card The server is not running, or it is MongoDB. Adminer does not support MongoDB, use mongosh or MongoDB Compass.

See also

WebDonkey view Premium

With Premium, the WebDonkey view is the alternative to Adminer on the Databases page. You see the tables of a database, page through the rows, edit, insert and delete, look at the structure, run SQL and export to a file. It all runs inside WebDonkey itself, with no login form and no password. The view exists for MySQL, MariaDB and PostgreSQL.

Where to find it

Sidebar Local › Databases. The header of the card at the bottom has the switch Adminer | WebDonkey view. Click WebDonkey view. WebDonkey remembers your choice, across app restarts too.

For MongoDB, WebDonkey view is greyed out and the tooltip says: “The WebDonkey view is there for MySQL, MariaDB and PostgreSQL.” For MongoDB the card stays with Adminer.

How to do it

  1. Pick the server at the top and start it if it is not running. While it is not running, the card says: “Start <server> above to see its data here.”
  2. Set the switch to WebDonkey view.
  3. Pick the Database at the top left. The database from Adminer opens with is preselected, otherwise the first one.
  4. Click a table on the left. Its rows appear on the right.

Card layout

Area Content
Header The title DB browser, the kind of server and the account the view works as (root@localhost:3306 or postgres@localhost:5432). On the right the switch and Refresh.
Left The Database picker, the Filter tables… field and the list of tables with an approximate row count.
Right The three tabs Data, Structure and SQL.

Drag the top or bottom edge of the card to change its height. WebDonkey remembers the height.

Data

The Data tab shows the rows of the selected table page by page.

  • Paging: the top right shows which rows you see and how many the table has. Rows per page picks 50, 100, 250 or 500 (default 100). Previous page and Next page page through.
  • Sorting: clicking a column header sorts ascending, a second click descending.
  • Filtering: type an SQL condition into the field after WHERE, for example `name` LIKE '%shirt%' on MySQL or "name" ILIKE '%shirt%' on PostgreSQL, and press Enter. The × (Clear filter) removes the filter.
  • Selecting: a click selects a row, ⌘-click adds more, ⇧-click selects a range.
  • Seeing a value: a cell's tooltip shows its content, up to 2,000 characters.

Edit, insert and delete rows

  • Edit: double-click a row to open Edit row.
  • Insert: Row (with a plus) opens New row.
  • Delete: select rows and click the trash can, which shows the number of selected rows. The confirmation says the rows are deleted right away and this cannot be undone.

Right-clicking a cell opens a menu: Edit row…, Duplicate row…, Delete row… (with several selected Delete n rows…), Copy value, Copy row(s) as CSV, Copy row(s) as JSON, Copy row(s) as INSERT, Filter: = this value and Filter: ≠ this value.

In a row's dialog every column is listed with its type. For each column you choose what gets stored:

Kind Meaning
Value The text in the field.
NULL Only for columns that allow NULL.
Default The server sets its default, such as the next ID.
SQL expression An expression like NOW() that the server evaluates.

Generated columns are marked computed, columns that cannot be changed read-only. Changed columns are highlighted, and the Undo change icon restores the old value. At the bottom Changed columns: n keeps count. Save or Insert writes the row. Afterwards a line above the table shows the result and the SQL WebDonkey ran.

Only tables with a primary key, or a unique key over columns without NULL, can be edited. Views and tables without such a key carry a lock badge and are read-only here. Change them with SQL.

Structure

The Structure tab shows the table from the inside:

  • Key figures such as type, engine, collation, rows, data, indexes, total, next id, created and updated, plus the key (primary key or unique key).
  • Columns (n) with Name, Type, NULL, Default, Key, Extra, Collation and Comment.
  • Indexes (n) and Foreign keys (n) with References.
  • DDL: the table's CREATE statement, with Copy.

SQL

  1. Switch to the SQL tab.
  2. Write the query, for example SELECT * FROM my_table LIMIT 20;. The line below names the database it runs in.
  3. Click Run or press ⌘↵.

Below the field you get the run time in milliseconds, Rows changed: n for statements that change data, and the result as a table. If a statement returns several result sets, you switch between them with Result 1, Result 2 and so on. Per result set WebDonkey shows at most the first 1,000 rows, the badge first n rows says so. History lists your last 30 queries on this server, a click puts one into the field.

Statements that can change data ask first: Change data on the server?. They run right away and cannot be undone. Run confirms.

Export

Export is available on the Data tab and below an SQL result.

  1. Choose at the top of the menu what gets exported: Shown rows (n), exactly what the table shows right now, or All rows, streamed from the server without the row limit, with the current filter and order.
  2. Choose the format: CSV, CSV (Excel), TSV, JSON, SQL INSERT, Markdown, HTML or XML.
  3. Click Copy to clipboard next to the format (shown rows only) or Save as file….

After saving, the menu shows the number of rows and the size of the file and Show in Finder. Cancel stops a long export.

What happens in the background

  • The view works as the server's admin account (root or postgres), just like WebDonkey itself. It sees every database, and every change applies at once.
  • Character set, backup and restore are not part of this card. You back up and restore in the database's row, see Backup and restore.
  • It is the same view as under Remote › Databases, pointed at your local servers.

Free and Premium

The WebDonkey view is Premium, as is the embedded Adminer. On Free there is no switch. You open Adminer in your browser with Open in browser there.

Troubleshooting

What you see What to do
WebDonkey view is greyed out The selected server is MongoDB. Use mongosh or MongoDB Compass.
“Pick a table on the left to browse its rows.” Click a table on the left.
No Row and no trash can, a lock instead The table is a view or has no key. Change it in the SQL tab.
The table shows nothing after filtering Check the condition. An error in the filter appears in place of the rows.

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy