Managing Tables, Columns, and Records

The NoCodeBackend Dashboard provides a built-in, spreadsheet-like interface for managing your live production data. This tool eliminates the need to configure third-party database clients.

This deep-dive guide explores how to alter your schema safely, manipulate raw records via the spreadsheet view, and utilize advanced filtering and bulk operations without writing SQL queries.

---

1. Detailed Overview

When you manage data in NoCodeBackend, you are interacting directly with your live MySQL instance.

The dashboard provides two distinct management interfaces:

1. Manage Tables (Schema Editor): This is where you execute structural operations. You add/remove tables and columns, and configure data types. These actions alter the fundamental structure of the database.
2. Manage Records (Data Editor): This is where you view, insert, update, and delete the actual rows of data residing within those tables.

Why built-in data management?

• Zero Configuration: Connecting a third-party tool requires managing IP whitelists, connection strings, SSL certificates, and database user credentials. Our dashboard bypasses this entirely.
• Safety Guards: The UI prevents you from executing destructive SQL commands accidentally (like dropping an entire table without confirmation) and ensures referential constraints are respected during manual data entry.

---

2. Step-by-Step Guide: Managing Data

Step 2.1: Modifying the Schema

As your application grows, you will inevitably need to add new fields to existing tables.

1. Go to your database dashboard and click Manage Tables.
2. Select the existing table you want to modify (e.g., users).
3. Click Add Column.
4. Define the new column (e.g., phone_number, Type: VARCHAR, Length: 20).
5. CRITICAL STEP: If your table already contains rows of data, you cannot mark this new column as "Required" unless you also provide a "Default Value". If you require it without a default, the database will throw an error because the existing rows would instantly become invalid.
6. Click Save. The REST API is instantly updated to accept and return the phone_number field.

Step 2.2: Interacting with the Spreadsheet View

1. Navigate to Manage Records.
2. Select the users table from the sidebar. You will see a data grid resembling Microsoft Excel.
3. Inserting Data: Click the + Add Row button. A modal appears enforcing the data types and required fields you set in the schema editor. Fill it out and click Save.
4. Editing Data (Inline): Double-click any individual cell in the grid. The cell transforms into an input field. Make your change and press Enter. The row flashes green, indicating the SQL UPDATE command was successfully executed against the database.
5. Deleting Data: Select the checkbox next to one or more rows. Click the red Delete button at the top of the grid.

---

3. Configuration & Parameters: Filtering and Sorting

When dealing with thousands of records, scrolling through the grid is inefficient. The Data Editor provides powerful querying parameters.

Sorting

• Click on any column header in the grid (e.g., created_at).
• The first click sorts the table by that column in Ascending order.
• The second click sorts it in Descending order (useful for finding the newest records).
• The third click removes the sort.

Advanced Filtering

1. Click the Filter button in the toolbar.
2. Click + Add Condition.
3. A condition consists of three parts:
   • Column: Select the field to evaluate (e.g., status).
   • Operator: Select the logic (e.g., equals, contains, greater than, is empty).
   • Value: Input the target data (e.g., active).
4. You can stack multiple conditions using AND / OR logic (e.g., status equals active AND price greater than 100).
5. Click Apply. The data grid updates immediately.

---

4. Best Practices & Edge Cases

• Handling Large Datasets: The Manage Records view utilizes server-side pagination. It only loads 50 records at a time. If you have a table with 10 million rows, the dashboard will remain perfectly fast and responsive. However, using a contains filter on an unindexed text column across 10 million rows will result in a slow query.
• Production Safety: Remember that any changes made here are instantly live. If you delete a user row here, that user will immediately lose access to your application. Always verify you are deleting the correct row.

---

5. Troubleshooting

Common Errors

Error: Cannot drop column 'status' because other objects depend on it.

• Cause: You attempted to delete a column from the Manage Tables interface, but you have a Pre Hook or Webhook configured that explicitly references that column name.
• Resolution: You must first delete or update the Pre Hook/Webhook logic before the database will allow you to destroy the column.

Error: UPDATE failed: numeric field overflow

• Cause: You attempted to type a massive number (e.g., 999999999999) into an inline cell that is configured as an INT type. The standard INT type maxes out at ~2.1 billion.
• Resolution: Change the column type to BIGINT via the Manage Tables interface if you expect numbers of that scale, or input a valid integer.

Error: Delete failed: violates foreign key constraint

• Cause: You attempted to delete a user who still has tasks assigned to them. The database blocks the deletion to prevent orphaned data.
• Resolution: You must either delete the dependent tasks first, or manage cascading logic at the application level.