Download the PHP package dbeurive/backend without Composer

On this page you can find all versions of the php package dbeurive/backend. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package backend

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? 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.

Overview

Generic overview

Contents

Additional notes


All versions of backend with dependencies

PHP Build Version
Package Version
Requires symfony/console Version *
dbeurive/input Version *
dbeurive/util Version >=1.0.18
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package dbeurive/backend contains the following files

Loading the files please wait ....