Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ContextMariaDb100133 does not exist

Open
#251 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
mariadb, php, sql
Domain
databases

Research direction

The issue names no repository file or test; begin by reproducing the LoaderException in the SQL parser and inspect how ContextMariaDb100133 is selected and loaded. Compare the requested context with the parser's supported MariaDB contexts, then verify that phpMyAdmin can open normally without the exception.

Written by the indexing model from the issue text.

Description

bug question

Suddenly when trying to use phpmyadmin, I am receiving the error below. Interestingly, I was in a debugging session debugging some php code. I went to use phpmyadmin and in the debugger context.php popped up. I closed out the debugger, tried to go to phpmyadmin and received this error. My database seems to be fine as I can get to it via the command line. I use phpmyadmin a lot so would like to get this working. How do I recover from it? Cheers, Michael

Fatal error: Uncaught PhpMyAdmin\SqlParser\Exceptions\LoaderException: Specified context ("\PhpMyAdmin\SqlParser\Contexts\ContextMariaDb100133") does not exist.

Dominant language
PHP
Stars
485
Forks
119
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phpmyadmin/sql-parser

All issues in phpmyadmin/sql-parser

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.