PHPackages                             dbeurive/backend - 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. dbeurive/backend

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

dbeurive/backend
================

This package contains the database interface

1.0.3(9y ago)025MITPHP

Since May 8Pushed 9y ago1 watchersCompare

[ Source](https://github.com/dbeurive/backend)[ Packagist](https://packagist.org/packages/dbeurive/backend)[ RSS](/packages/dbeurive-backend/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependencies (4)Versions (19)Used By (0)

- [Introduction](#a0)
- [Overview](#a1)
- [Contents](#a2)
- [Additional notes](#a3)

Introduction
==========================================

[](#introduction)

Although ORM exist, using SQL is a valid strategy.

There is no « one size fits all approach ». There are many ways to access data from an application. The three mostly used techniques are : stored procedures, direct SQL within the application’s code, and ORM. Each of these techniques present advantages and drawbacks, depending on the context (the size of the company, the type of projects...). And one should not start using an ORM just because it is the « universally recommended » choice (by the creator of the ORM), or because it is part of the default framework’s distribution.

In many situations, using SQL is a far better solution than using an ORM.

This project is an attempt to make using SQL an even more pragmatic approach by providing a simple way to organise and to document SQL.

What does this is all about ?

This is all about documentation. Please read: [why did I write this database access layer?](https://github.com/dbeurive/backend/blob/master/doc/WHY.md)If you access your database through this API, then you can get a SQLite database that organises all information about your SQL requests and your procedures.

- Click [here](https://github.com/dbeurive/backend/blob/master/src/Database/Doc/schema.php) to get the schema for the generated SQLite database.
- You can download an example of the generated database [here](https://github.com/dbeurive/backend/blob/master/tests/cache/mysql_doc.sqlite).
- Click [here](https://github.com/dbeurive/backend/blob/master/doc/SQLITE_USAGE.md) to have an overview of what you can do with the SQLite database that contains the generated documentation.

Overview
======================================

[](#overview)

[![Generic overview](https://github.com/dbeurive/backend/raw/master/doc/overview.png)](https://github.com/dbeurive/backend/blob/master/doc/overview.png)

Contents
======================================

[](#contents)

- [Installation notes](https://github.com/dbeurive/backend/blob/master/doc/INSTALL.md)
- [Writing and using SQL requests and procedures](https://github.com/dbeurive/backend/blob/master/src/Database/EntryPoints/README.md)
- [Documenting SQL requests and procedures](https://github.com/dbeurive/backend/blob/master/src/Database/EntryPoints/Description/README.md)
- [Using the database interface](https://github.com/dbeurive/backend/blob/master/src/Database/README.md)
- [Generating the database's access layer documentation](https://github.com/dbeurive/backend/blob/master/src/Cli/Bin/README.md) - that is: the SQLite database.
- See this utility to manipulate MySql SQL requests: [UtilMySql::developSql()](https://github.com/dbeurive/util/blob/master/README.md)

Additional notes
==============================================

[](#additional-notes)

- [Using the Makefile](https://github.com/dbeurive/backend/blob/master/doc/MAKEFILE.md)

###  Health Score

29

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity72

Established project with proven stability

 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 ~14 days

Recently: every ~58 days

Total

18

Last Release

3462d ago

Major Versions

0.0.23 → 1.0.02016-05-18

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/18211524?v=4)[Denis BEURIVE](/maintainers/dbeurive)[@dbeurive](https://github.com/dbeurive)

---

Top Contributors

[![dbeurive](https://avatars.githubusercontent.com/u/18211524?v=4)](https://github.com/dbeurive "dbeurive (79 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/dbeurive-backend/health.svg)

```
[![Health](https://phpackages.com/badges/dbeurive-backend/health.svg)](https://phpackages.com/packages/dbeurive-backend)
```

###  Alternatives

[perplorm/perpl

Perpl is an improved and still maintained fork of Propel2, an open-source Object-Relational Mapping (ORM) for PHP.

249.4k](/packages/perplorm-perpl)

PHPackages © 2026

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