Conversation with Gemini

To run Clutch on Emacs under FreeBSD to manage MySQL databases, you need to configure your package archives, install the Clutch core along with its MySQL protocol driver, and configure your connection.

Step 1: Configure Package Archives (MELPA)

If you haven't set up MELPA in Emacs yet, add the repository to your Emacs initialization file (~/.emacs, ~/.emacs.d/init.el, or ~/.config/emacs/init.el):

(require 'package)
(add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t)
(package-initialize)

Evaluate the code or restart Emacs, then fetch the latest package lists:

M-x package-refresh-contents

Step 2: Install Clutch and the MySQL Backend

Clutch requires a separate backend package (mysql.el) to handle MySQL protocol operations.

1. Install Clutch:

   GitHub
   Plaintext

   M-x package-install RET clutch RET
   

2. Install the MySQL protocol backend:

   GitHub
   Plaintext

   M-x package-install RET mysql RET
   

(Alternatively, if using use-package, add the following to your init file):

(use-package mysql
  :ensure t)

(use-package clutch
  :ensure t
  :after mysql)

Step 3: Configure Your MySQL Connection

Define your FreeBSD or remote MySQL connections in your init file using clutch-connection-alist:

(setq clutch-connection-alist
      '(("my-freebsd-db"
         :backend mysql
         :host "127.0.0.1"
         :port 3306
         :user "db_user"
         :database "my_database")))

Note on Passwords: You can pass :password "your_password" in the connection parameters. However, leaving :password out is recommended; Clutch will securely attempt to look up your credentials via auth-source (~/.authinfo.gpg or pass) or prompt you interactively when connecting.

Step 4: Connecting and Editing MySQL Tables

SELECT * FROM users;

The behavior you are seeing occurs because clutch-connect establishes the connection state asynchronously and echoes a confirmation message (e.g., [Clutch] Connected to my-freebsd-db), but does not automatically spawn a new SQL buffer by default.

Here is how to open the query console, execute SQL, and get into the row-editing grid:

Step 4 (Corrected): Connecting, Querying, and Editing

1. Open the Query Console Buffer

After running M-x clutch-connect and selecting your connection:

• If you already have a .sql file or SQL buffer open, Clutch attaches to that buffer.

  GitHub

• To open a dedicated Clutch query console manually, run:

  Plaintext

  M-x clutch-query
  

  (Or M-x clutch-open-console depending on your Clutch version). Select your active connection (my-freebsd-db).

2. Run a Query

In the opened SQL buffer, type your target query:

SELECT * FROM your_table_name;

With point anywhere on the SQL statement (or with the statement region highlighted), press:

C-c C-c

This sends the query to the server, splits the window, and opens the interactive result grid in a lower window.

3. Stage Your Edits in the Grid

Switch focus to the results buffer (C-x o):

• Edit Cell: Position point on any value and type directly to modify it.

  GitHub

• Insert Row: Press o to add a new staged row at the end.

• Delete Row: Press d to mark the current row for deletion.

4. Preview and Commit Changes

Modified cells and pending operations will be highlighted.

• Press C-c C-c inside the grid buffer to open the change preview.

• Confirm the generated UPDATE / INSERT / DELETE statements to execute them against MySQL.

  GitHub

In Clutch, the message row editing unavailable E/D off (or row identity missing: Edit/Delete disabled) means that Clutch has placed the results buffer in read-only mode because it cannot safely identify individual rows to target with standard UPDATE or DELETE SQL statements.

This safety guardrail triggers automatically under two main scenarios:

1. The Query Missing a Row Identity (Most Common)

Clutch needs a unique row identity (usually a Primary Key) in your SELECT projection to map an edit in the Emacs buffer back to a specific record in MySQL.

• No Primary Key in SELECT: If you run SELECT name, email FROM users; (leaving out id), Clutch cannot guarantee which specific row to update, so it disables editing.

  • Fix: Make sure your SELECT query includes the Primary Key column(s):

    SQL

    SELECT id, name, email FROM users;
    

• Table has no Primary Key: If the underlying database table lacks a Primary Key, Clutch treats the result set as read-only.

  • Fix: Add a Primary Key to the table via DDL:

    SQL

    ALTER TABLE users ADD PRIMARY KEY (id);
    

2. Derived, Aggregated, or Joined Result Sets

Clutch only permits live grid editing on direct single-table projections.

• Aggregations / Groups: Queries using GROUP BY, COUNT(), SUM(), or DISTINCT cannot be edited.

• Joins: Multi-table JOIN query results are ambiguous for direct inline updates and will default to E/D off.

• Calculated Columns: Selecting alias columns like SELECT id, price * 1.1 AS marked_up FROM products; will render the result set non-editable.

How to Enable Editing

To get row editing working, run a simple, direct selection of a table containing a primary key while explicitly selecting that key column:

SELECT * FROM your_table_name;

Once executed with C-c C-c, the E/D off indicator should clear, allowing you to edit values, stage new rows with o, or mark rows for deletion with d.

This video on fixing MySQL table data edit issues demonstrates how missing primary keys cause database tools to lock down table editing to read-only mode.

Unable to edit table data SOLVED in Mysql Workbench | Change read only mode manually

United Top Tech · 8.3K views

Open in Unable to edit table data SOLVED in Mysql Workbench | Change read only mode manually