| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 2850 |
| Technical Name |
no_dev_console |
| License | OPL-1 |
| Website | https://www.oudayet.com |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 2850 |
| Technical Name |
no_dev_console |
| License | OPL-1 |
| Website | https://www.oudayet.com |
| Versions | 17.0 18.0 19.0 |
Developer Console.
Run SQL in Odoo — with rails, not regrets.
Schema browser, multi-tab SQL editor, per-operation capabilities, append-only audit log.
Odoo 17 READ-ONLY BY DEFAULT $89.99 USD 9 LanguagesA real data console, not a <textarea>
Most SQL-runner modules are a blank box and a Run button. No schema, no safety, no record of who ran what. Developer Console gives you a proper workspace with server-side guard rails and an audit trail.
A typical SQL executor
Paste a query, hit Run, hope you don’t drop a table by accident. You memorise table names, there’s no audit, and everyone with access can do everything.
Developer Console
Browse the schema, run SQL under per-operation capabilities, read-only enforced by PostgreSQL itself, and every execution logged to an append-only audit trail.
Everything you need to work with the data
One workspace: explore, query, save, export — safely.
Every non-transient Odoo model mapped to its real PostgreSQL table and columns. One click drops SELECT * FROM <table> LIMIT 100 into the editor.
Line numbers, SQL-aware highlighting, autocomplete, and a multi-tab workspace. Press Ctrl+Enter to run.
Five independent groups — SELECT, INSERT, UPDATE, DELETE, DDL — plus one-click User (read-only) and Manager (full) presets. Granting one never auto-grants another.
For SELECT-only users the query runs under transaction_read_only = on and is always rolled back — even a write hidden in a function call is refused by PostgreSQL itself.
Every attempt — success, blocked, or error — recorded with user, kind, rows, duration and status. Immutable: no group, not even Manager, can edit or delete entries.
Keep reusable queries with categories — private or shared, owner-only edit. Export any result to CSV, JSON, XLSX or Markdown, or the raw query text.
See it in action
From schema to query to audit — the whole workflow, with the rails always on.
Multi-tab SQL editor — syntax highlighting, autocomplete, results grid. Press Ctrl+Enter to run.
Schema browser — every Odoo model mapped to its PostgreSQL table; one click drops a SELECT into the editor.
Per-operation capabilities — grant SELECT / INSERT / UPDATE / DELETE / DDL independently: presets or tailored Custom sets.
Server-side safety rails — a read-only user’s DELETE is refused before it runs, with a clear message.
Append-only audit log — every attempt with user, kind, rows, duration and Success / Blocked / Error.
Saved-query library — reusable, categorized queries, private or shared.
How a query is kept safe
A string/comment-aware tokeniser scans the whole query, rejects multi-statement input, and computes exactly which capabilities it needs — including writes hidden in CTEs or SELECT INTO.
The user must hold every required capability. A denylist blocks side-effecting functions (filesystem, connection control, cross-database) that could sidestep row-level checks.
The query runs inside a savepoint; read-only sessions always roll back. The attempt is written to the audit log — even if it was blocked.
Available in 9 Languages
Every label, button and message is translated — each user sees the console in their own Odoo language, no extra setup.
English
Français
Español
Deutsch
Nederlands
Português (BR)
Italiano
中文
العربيةHonest scope
✗ This is a power tool. Access is never self-service — only an administrator can grant the capability groups. Don’t hand it to end users.
Writes (for capable users) run as one statement at a time under your DB role’s own privileges. For schema migrations use proper Odoo modules; use this to inspect, fix and report.
Safety is enforced on the server
The rails are not UI hints. Capability checks, the multi-statement guard, the function denylist and transaction_read_only all run in the Python controller and PostgreSQL — not the browser. A user with only the SELECT capability cannot write, full stop, and every attempt is recorded in an audit log nobody can delete.
FAQ
No. SELECT-only sessions run under transaction_read_only = on and always roll back, so PostgreSQL itself blocks any write — including writes hidden inside function calls or data-modifying CTEs.
Only users explicitly granted those capabilities. DELETE is separate from UPDATE so you can allow data fixes without allowing row removal.
Best on self-hosted or Odoo.sh where you control the database. The module runs SQL against your Odoo PostgreSQL database under its existing role.
Yes — every execution attempt (success, blocked, or error) with user, query, kind, rows, duration and status. The log is append-only and survives even blocked queries.
Technical details
© Naim OUDAYET — oudayet.com — OPL-1 license
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module