Aura.Sql alternatives and similar libraries
Based on the "Database" category.
Alternatively, view Aura.Sql alternatives based on common mentions on social networks and blogs.
8.8 8.0 L4 Aura.Sql VS Doctrine ExtensionsDoctrine2 behavioral extensions, Translatable, Sluggable, Tree-NestedSet, Timestampable, Loggable, Sortable
8.2 9.1 L4 Aura.Sql VS Eloquent[READ ONLY] Subtree split of the Illuminate Database component (see laravel/framework)
7.2 7.3 L3 Aura.Sql VS PropelPropel2 is an open-source high-performance Object-Relational Mapping (ORM) for modern PHP
6.6 4.9 Aura.Sql VS Doctrine2 BehaviorsDoctrine2 behavior traits that help handling Blameable, Loggable, Sluggable, SoftDeletable, Uuidable, Timestampable, Translatable, Tree behavior
5.4 0.0 L5 Aura.Sql VS Spot2Spot v2.x DataMapper built on top of Doctrine's Database Abstraction Layer
5.0 2.1 Aura.Sql VS Aura.SqlQueryIndependent query builders for MySQL, PostgreSQL, SQLite, and Microsoft SQL Server.
4.5 0.6 Aura.Sql VS Atlas.OrmA data mapper implementation for your persistence model in PHP.
3.3 0.0 L3 Aura.Sql VS Cake ORM[READ-ONLY] A flexible, lightweight and powerful Object-Relational Mapper for PHP, implemented using the DataMapper pattern. This repo is a split of the main code that can be found in https://github.com/cakephp/cakephp
1.3 0.0 Aura.Sql VS LDBAHigh-performance, low-memory-footprint, single-file embedded database for key/value storage
A working Firebase http client
0.7 0.0 L3 Aura.Sql VS LazyRecordThe fast ORM for PHP. (This is a history repo, please visit maghead/maghead)
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Aura.Sql or a related project?
Provides an extension to the native PDO along with a profiler and connection locator. Because ExtendedPdo is an extension of the native PDO, code already using the native PDO or typehinted to the native PDO can use ExtendedPdo without any changes.
Added functionality in Aura.Sql over the native PDO includes:
Lazy connection. ExtendedPdo connects to the database only on method calls that require a connection. This means you can create an instance and not incur the cost of a connection if you never make a query.
Decoration. DecoratedPdo can be used to decorate an existing PDO instance. This means that a PDO instance can be "extended" at runtime to provide the ExtendedPdo behaviors.
Array quoting. The
quote()method will accept an array as input, and return a string of comma-separated quoted values.
perform()method acts just like
query(), but binds values to a prepared statement as part of the call. In addition, placeholders that represent array values will be replaced with comma- separated quoted values. This means you can bind an array of values to a placeholder used with an
IN (...)condition when using
fetch*()methods. The new
fetch*()methods provide for commonly-used fetch actions. For example, you can call
fetchAll()directly on the instance instead of having to prepare a statement, bind values, execute, and then fetch from the prepared statement. All of the
fetch*()methods take an array of values to bind to to the query statement, and use the new
yield*()methods. These are complements to the
yieldresults instead of
Exceptions by default. ExtendedPdo starts in the
ERRMODE_EXCEPTIONmode for error reporting instead of the
Profiler. An optional query profiler is provided, along with an interface for other implementations, that logs to any PSR-3 interface.
Connection locator. A optional lazy-loading service locator is provided for picking different database connections (default, read, and write).
Installation and Autoloading
This package is installable and PSR-4 autoloadable via Composer as aura/sql.
Alternatively, download a release, or clone this repository, then map the
Aura\Sql\ namespace to the package
This package requires PHP 5.6 or later; it has also been tested on PHP 7 and HHVM. We recommend using the latest available version of PHP as a matter of principle.
Aura library packages may sometimes depend on external interfaces, but never on external implementations. This allows compliance with community standards without compromising flexibility. For specifics, please examine the package [composer.json] file.
This project adheres to Semantic Versioning.
To run the unit tests at the command line, issue
composer install and then
./vendor/bin/phpunit at the package root. (This requires Composer to be
This package is fully documented [here](./docs/index.md).