MySQL

How to Understand Which Queries Are Blocked for Security

Learn which SQL queries are blocked on Nobregas Panel and why. Security restrictions, blocked operations, and safe alternatives explained.

3 min read 26 views Updated Mar 17, 2026

The Nobregas MySQL Panel restricts certain SQL operations to protect your databases and the shared hosting environment. Understanding which queries are blocked — and why — helps you work within the system safely and find alternative approaches.

Why Some Queries Are Blocked

The panel runs on a managed MySQL hosting platform where:

  • Multiple users share server resources.
  • Accidentally destructive operations could cause irreversible damage.
  • Certain administrative commands could affect other users on the same server.
  • The UI provides safer alternatives for dangerous operations.

Blocking dangerous queries at the application level adds a safety net beyond MySQL's own privilege system.

Blocked Operations

User and Privilege Commands

Blocked Query Reason Alternative
GRANT Privilege management is handled by the UI Use the Manage button on the Database Users page
REVOKE Privilege management is handled by the UI Use the Manage button to revoke access
CREATE USER User creation is managed through the panel Use the Create User button on Database Users
DROP USER User deletion is managed through the panel Use the Delete button on Database Users
ALTER USER User modification is managed through the panel Use the panel's user management features
SET PASSWORD Password changes are managed through the panel Delete and recreate the user with a new password

Server-Level Commands

Blocked Query Reason Alternative
FLUSH Server-wide impact Not available on shared hosting
RESET Server-wide impact Not available on shared hosting
SHUTDOWN Would stop the server for all users Not available

What You Can Still Run

The vast majority of SQL operations are fully supported:

  • All data queries: SELECT, INSERT, UPDATE, DELETE
  • Table management: CREATE TABLE, ALTER TABLE, DROP TABLE, TRUNCATE TABLE
  • Index operations: CREATE INDEX, DROP INDEX
  • View management: CREATE VIEW, DROP VIEW
  • Stored procedures: CREATE PROCEDURE, CALL, DROP PROCEDURE
  • Transaction control: BEGIN, COMMIT, ROLLBACK
  • Information queries: SHOW TABLES, DESCRIBE, EXPLAIN, SHOW CREATE TABLE

How to Know If Your Query Was Blocked

When you run a blocked query, the panel returns a clear error message:

  • The message identifies that the operation is restricted for security.
  • It explains why the operation is blocked.
  • It suggests the alternative method to achieve the same result through the UI.

Tips for Working Within Restrictions

  • Use the UI for user and privilege management — it is the safe and intended way.
  • DROP TABLE is allowed in the query editor — you can manage tables via SQL.
  • TRUNCATE TABLE is allowed — you can empty tables from the query editor.
  • DROP DATABASE is allowed in the query editor — but consider using the Databases page for safety.
  • If you need a blocked operation, check whether the panel's UI provides the equivalent feature.

Was this article helpful?