Query editor

The query editor lets you run SQL against the connected PostgreSQL database.

Common query examples​

SELECT * FROM bookings LIMIT 10;

SELECT status, COUNT(*)
FROM bookings
GROUP BY status
ORDER BY status;

SELECT rooms.name, rooms.price_per_night
FROM rooms
ORDER BY rooms.price_per_night DESC;

Run a query​

1. Open the database tool from the workspace.
2. Choose Query.
3. Write a focused SQL statement.
4. Execute it.
5. Review the result table.
6. Save the query externally if it is useful for later testing.

Query workflow​

Use the query editor as a verification tool:

1. Confirm the table exists.
2. Count records.
3. Inspect recent rows.
4. Check status values and ownership fields.
5. Join related tables when a screen depends on relationships.
6. Ask Cocoding AI to update the app only after you know which data is wrong.

Useful checks​

Read-only recipes​

SELECT COUNT(*) FROM bookings;

SELECT status, COUNT(*)
FROM payments
GROUP BY status;

SELECT b.id, b.status, u.email
FROM bookings b
JOIN users u ON u.id = b.user_id
ORDER BY b.created_at DESC
LIMIT 20;

Query safely​

• Start with SELECT queries.
• Use LIMIT when inspecting large tables.
• Avoid destructive statements unless you are in a test database.
• Keep a copy of important data before bulk updates.
• Avoid running copied SQL if you do not understand what it changes.
• Do not paste production data exports into chat.

Keyboard shortcut​

Use Cmd + Enter on macOS or Ctrl + Enter on Windows/Linux when the query editor supports quick execution.

Troubleshooting query results​