Project Description

Schema Viewer is a developer-friendly Drupal module that allows site builders and developers to view the schema (structure) of database tables used within a Drupal installation, without exposing any table data. The module provides an intuitive interface for inspecting table columns, data types, lengths, nullability, and indexes.

Key features:

  • Autocomplete-based table name search.
  • Displays the full table schema in a clean, readable format.
  • Only accessible to users with appropriate permissions (e.g., site administrators).
  • Supports filtering tables by name to make navigation easier.
  • Built entirely using Drupal Form API for seamless admin integration.
  • Supports multiple Drupal core versions: 9.x, 10.x, and 11.x.

How this module is different from similar projects:

While there are other tools (like Devel module or external DB clients) that expose table data or debugging information:
Schema Viewer is focused exclusively on schema visibility, without showing or exposing any data.
It does not require external access to the database or external tools like phpMyAdmin.
Offers filterable, search-based viewing, helping developers focus only on specific tables they are working with.
It is safer for use in shared environments since no CRUD operation or sensitive data exposure occurs.

Install and enable the module:

Place the schema_viewer module inside your site's modules/custom/ directory.
Enable the module via:
Admin UI: Go to Extend (/admin/modules), search for Schema Viewer, and enable it.
Or
use Drush:
drush en schema_viewer
Navigate to the module interface:

In your browser, go to:
/admin/config/development/schema-viewer
Or via menu:
Administration → Configuration → Development → Schema Viewer

Use the interface:
Start typing a table name in the autocomplete search box.
Select the table you want to inspect.
The schema (column names, data types, lengths, null constraints, and indexes) will be displayed in a readable format.

Project link

https://www.drupal.org/project/schema_viewer

Comments

mismail.drupal created an issue. See original summary.

mismail.drupal’s picture

mismail.drupal commented
Issue summary: View changes
vishal.kadam’s picture

vishal.kadam
Location Mumbai
commented
Issue summary: View changes
shubham_pareek_19’s picture

shubham_pareek_19 commented
Assigned: Unassigned » shubham_pareek_19

Working on it.

shubham_pareek_19’s picture

shubham_pareek_19 commented
Assigned: shubham_pareek_19 » Unassigned

I had mistakenly assigned this issue to myself. Unassigning now apologies for the confusion.

vishal.kadam’s picture

vishal.kadam
Location Mumbai
commented

Only the person who created the application will be responsible for implementing the reviewers' suggested changes and committing them.

mismail.drupal’s picture

mismail.drupal commented

Hi @vishal.kadam,

As I am new to contributing a Drupal module, do I need to assign someone to review it, or will it be reviewed automatically by the Drupal team?

please hep on this.

mismail.drupal’s picture

mismail.drupal commented
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Thank you for applying!

Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.

The important notes are the following.

  • If you have not done it yet, enable GitLab CI for the project, and fix what reported from the phpcs job. This help to fix most of what reviewers would report.
  • For the time this application is open, only your commits are allowed. No other people, including other maintainers/co-maintainers can make commits.
  • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application.
  • Nobody else will get the permission to opt projects into security advisory policy. If there are other maintainers/co-maintainers who will to get that permission, they need to apply with a different module.
  • We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

To the reviewers

Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.

The important notes are the following.

  • It is preferable to wait for a Code Review Administrator before commenting on newly created applications. Code Review Administrators will do some preliminary checks that are necessary before any change on the project files is suggested.
  • Reviewers should show the output of a CLI tool only once per application. The configuration used for these tools needs to be the same configuration used by GitLab CI, stored in the GitLab Templates repository.
  • It may be best to have the applicant fix things before further review.

For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Needs review » Needs work

Usually, after reviewing a project, we allow the developer to opt projects into security advisory coverage. This project is too small for us; it does not contain enough PHP code to really assess your skills as a developer.

Do you have any other project hosted on drupal.org that we could instead review? It needs to have most of the commits (but preferably all the commits) done by you, in at least a branch.

mismail.drupal’s picture

mismail.drupal commented
Status: Needs work » Needs review

Hello @avpaderno

I would like to confirm that phpcs has already been run locally, and all issues have been fixed before pushing to the Drupal.org branch.

As I’m still new to contributing, please do let me know if I’ve missed anything or if any further changes are needed.

Thank you for your time and guidance.

Best regards,

bbu23’s picture

bbu23
Location 🇪🇺🇪🇺🇪🇺
commented
Status: Needs review » Needs work

The question in #10 is still unanswered.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Priority: Normal » Minor

I am changing priority as per Issue priorities.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

This thread has been idle, in the needs work state with no activity for some months.

May you confirm you are still pursuing this application? If this is the case, and you made commits basing on what previously reported, or you can answer the questions previously asked, please change the status to Needs review.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Needs work » Closed (won't fix)

This thread has been idle, in the Needs work state with no activity for about six months or more; the application has been created about 11 months ago or more. Therefore, I marked it as Closed (won't fix).

If this is incorrect, and you are still pursuing this application, please feel free to re-open it and set the issue status to Needs work or Needs review, depending on the current status of your code.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.