PHPackages                             lbreme/lexepa-sql - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Database & ORM](/categories/database)
4. /
5. lbreme/lexepa-sql

ActiveLibrary[Database & ORM](/categories/database)

lbreme/lexepa-sql
=================

Library for lexing and parsing a SQL INSERT statement

v1.0.2(5y ago)07MITPHPPHP >=7.0.0

Since May 19Pushed 5y ago1 watchersCompare

[ Source](https://github.com/lbreme/lexepa-sql)[ Packagist](https://packagist.org/packages/lbreme/lexepa-sql)[ Docs](https://github.com/lbreme/lexepa-sql)[ RSS](/packages/lbreme-lexepa-sql/feed)WikiDiscussions main Synced 3w ago

READMEChangelog (3)DependenciesVersions (4)Used By (0)

Lexepa-Sql
==========

[](#lexepa-sql)

Library for lexing and parsing a SQL INSERT query.

Installing Lexepa-Sql
=====================

[](#installing-lexepa-sql)

First, get [Composer](https://getcomposer.org/download/), if you don't already use it.

Next, run the following command inside the directory of your project:

```
composer require lbreme/lexepa-sql
```

How does it work?
=================

[](#how-does-it-work)

The Lexepa-Sql library analyzes any file that contains one or more INSERT SQL queries. During the analysis a series of callback functions are called to which the elements that constitute the query are passed as arguments.

Let's clarify with an example, which is contained in the file [class-example-sql.php](https://github.com/lbreme/lexepa-sql/blob/main/class-example-sql.php), which to make it work is to copy in the root of your project, along with the test file [insert.sql](https://github.com/lbreme/lexepa-sql/blob/main/insert.sql):

```
/*
We create a class derived from the Lexepa_Sql_Abstract class, which implements all the
callback functions that will be called by the analysis of the SQL INSERT query
*/
class Example_Sql extends Lexepa_Sql_Abstract
{
	/**
	 * Begin of the SQL INSERT query.
	 *
	 * @param int    $begin_offset Offset of the SQL INSERT query.
	 */
	public function begin_insert( $begin_offset )
	{
		echo 'Offset of the SQL INSERT query: ' . $begin_offset . '';
	}

	/**
	 * Table name found
	 *
	 * @param string $table_name Table name.
	 * @param int    $offset Offset of the table name.
	 */
	public function table_name( $table_name, $offset )
	{
		echo 'Table name: ' . $table_name . '';
	}

	/**
	 * Field name found
	 *
	 * @param string $field_name Field name.
	 * @param int    $offset Offset of the field name.
	 */
	public function field_name( $field_name, $offset )
	{
		echo 'Field name: ' . $field_name . '';
	}

	/**
	 * Field value found
	 *
	 * @param string $field_value Field value.
	 * @param int    $offset Offset of the field value.
	 */
	public function field_value( $field_value, $offset )
	{
		echo 'Field value: ' . $field_value . '';
	}

	/**
	 * End of the SQL INSERT query
	 *
	 * @param int $end_offset Offset of the end of the SQL INSERT query.
	 */
	public function end_insert( $end_offset )
	{
		echo 'Offset of the end of the SQL INSERT query: ' . $end_offset . '';
	}

	/**
	 * End of the file parsing
	 *
	 * @param bool $offset Offset of the end of the file parsing.
	 */
	public function end_parsing( $offset )
	{
		echo 'Offset of the end of the file parsing: ' . $offset . '';
	}

	/**
	 * Set error parsing the file.
	 *
	 * @param string $error Error parsing the file.
	 */
	public function set_error( $error )
	{
		echo $error . '';
	}
}

$example_sql = new Example_Sql();

/*
We instantiate the Lexepa-Sql library class, passing as arguments the $example_sql object
containing the callback functions and the file name to be parsed
*/
$lexepa_sql  = new Lexepa_Sql( $example_sql, 'insert.sql' );

// Let's start the analysis
$lexepa_sql->parse_sql();

```

The result of this example is as follows:

```
Offset of the begin of the SQL INSERT query: 0
Table name: wp_options
Field value: 1
Field value: siteurl
Field value: https://www.mysite.com/
Field value: yes
Field value: 2
Field value: home
Field value: https://www.mysite.com/
Field value: yes
Field value: 3
Field value: blogname
Field value: My site
Field value: yes
Field value: 4
Field value: blogdescription
Field value: My revised site
Field value: yes
Offset of the end of the SQL INSERT query: 206
Offset of the begin of the SQL INSERT query: 208
Table name: wp_postmeta
Field value: 71
Field value: 33
Field value: _edit_last
Field value: 1
Field value: 72
Field value: 33
Field value: adventurous-header-image
Field value: default
Field value: 73
Field value: 33
Field value: adventurous-sidebarlayout
Field value: default
Field value: 74
Field value: 33
Field value: adventurous-featured-image
Field value: default
Field value: 75
Field value: 33
Field value: _edit_lock
Field value: 1600100291:1
Field value: 76
Field value: 35
Field value: _edit_last
Field value: 1
Offset of the end of the SQL INSERT query: 489
Offset of the end of the file parsing: 491
```

The callback functions implemented by the Lexepa\_Sql\_Abstract class are contained and documented in the interface file [class-lexepa-sql-interface.php](https://github.com/lbreme/lexepa-sql/blob/main/src/class-lexepa-sql-interface.php)

###  Health Score

22

—

LowBetter than 21% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity4

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

3

Last Release

1861d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/e380285a4f2d8c072971dfa95aa842885c5e7da9dbe0486f4c4bd909fc7aeb38?d=identicon)[wpandphplover](/maintainers/wpandphplover)

---

Top Contributors

[![lbreme](https://avatars.githubusercontent.com/u/66303392?v=4)](https://github.com/lbreme "lbreme (1 commits)")

---

Tags

parsersqllexerinsert

### Embed Badge

![Health badge](/badges/lbreme-lexepa-sql/health.svg)

```
[![Health](https://phpackages.com/badges/lbreme-lexepa-sql/health.svg)](https://phpackages.com/packages/lbreme-lexepa-sql)
```

###  Alternatives

[phpmyadmin/sql-parser

A validating SQL lexer and parser with a focus on MySQL dialect.

48051.5M70](/packages/phpmyadmin-sql-parser)[greenlion/php-sql-parser

A pure PHP SQL (non validating) parser w/ focus on MySQL dialect of SQL

64112.1M94](/packages/greenlion-php-sql-parser)[aura/sqlquery

Object-oriented query builders for MySQL, Postgres, SQLite, and SQLServer; can be used with any database connection library.

4563.1M37](/packages/aura-sqlquery)[timgws/query-builder-parser

Build complex Eloquent & QueryBuilder queries automatically when using jQuery-QueryBuilder

161399.7k](/packages/timgws-query-builder-parser)[sad_spirit/pg_builder

Query builder for Postgres backed by SQL parser

5936.4k1](/packages/sad-spirit-pg-builder)[nilportugues/sql-query-formatter

A very lightweight PHP class that reformats unreadable and computer-generated SQL query statements to human-friendly, readable text.

381.1M27](/packages/nilportugues-sql-query-formatter)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)