Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7902963
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T09:38:26+00:00 2026-06-03T09:38:26+00:00

I have a row in a table that I do not want to be

  • 0

I have a row in a table that I do not want to be changed (ever).

Is it possible to set a MySQL row to READ-ONLY so that it cannot be updated in any way? If so, how?

If not, is it possible to set a permanent value in one of the columns of that row so that it cannot be changed? If so, how?

Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-03T09:38:27+00:00Added an answer on June 3, 2026 at 9:38 am

    This is likely to be business logic, which probably doesn’t belong in your data storage layer. However, it can nonetheless be accomplished using triggers.

    You can create a BEFORE UPDATE trigger that raises an error if a “locked” record is about to be updated; since an error occurs before the operation is undertaken, MySQL ceases to proceed with it. If you also want to prevent the record from being deleted, you’d need to create a similar trigger BEFORE DELETE.

    To determine whether a record is “locked”, you could create a boolean locked column:

    ALTER TABLE my_table ADD COLUMN locked BOOLEAN NOT NULL DEFAULT FALSE;
    
    DELIMITER ;;
    
    CREATE TRIGGER foo_upd BEFORE UPDATE ON my_table FOR EACH ROW
    IF OLD.locked THEN
      SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Cannot update locked record';
    END IF;;
    
    CREATE TRIGGER foo_del BEFORE DELETE ON my_table FOR EACH ROW
    IF OLD.locked THEN
      SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Cannot delete locked record';
    END IF;;
    
    DELIMITER ;
    
    UPDATE my_table SET locked = TRUE WHERE ...;
    

    Note that SIGNAL was introduced in MySQL 5.5. In earlier versions, you must perform some erroneous action that causes MySQL to raise an error: I often call an non-existent procedure, e.g. with CALL raise_error;


    I cannot create an additional column on this table, but the row has a unique id in one of the columns, so how would I do this for that scenario?

    Again, if you absolutely must place this logic in the storage layer—and cannot identify the locked records through any means other than the PK—you could hard-code the test into your trigger; for example, to “lock” the record with id_column = 1234:

    DELIMITER ;;
    
    CREATE TRIGGER foo_upd BEFORE UPDATE ON my_table FOR EACH ROW
    IF OLD.id_column <=> 1234 THEN
      SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Cannot update locked record';
    END IF;;
    
    CREATE TRIGGER foo_del BEFORE DELETE ON my_table FOR EACH ROW
    IF OLD.id_column <=> 1234 THEN
      SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Cannot delete locked record';
    END IF;;
    
    DELIMITER ;
    

    But this is absolutely horrible and I would do almost anything to avoid it whenever possible.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We have a 10 thousand row table that has just 2 columns, a primary
I have a table row that needs to be hidden when the anchor with
I have a table row that has the error message in it. <tr runat=server
I have a table that is accessed by row and column, where those two
I have a table row, and within that, I have a td (whatever it
I have a multi-row insert that looks something like: insert into table VALUES (1,
I have a schema design that looks like this: Table: User Row Column Family
I have a function that allows users to edit a row in a table
I have a function that is to run through each row of a table,
Is it possible to have a table and insert data n a single row

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.