Libraries tagged by query tools

DoctrineORM Resources to ZF3

Go to Download

Quickly create an automatic API CRUD with your Doctrine ORM connection

Go to Download

a simple extended pdo tool library of the php

Go to Download

Dataman is a simple database manager using PDO that simplifies back-end processing and grants with useful tools.

Go to Download

Composer library to query AWS SES notifications (SQS queues)

Go to Download

PDO Query Tools

Go to Download

Bank query tool.

Go to Download

Telegram integration for Craft CMS - Send event messages to Telegram chats and execute GraphQL queries and other tools provided in a telegram bot interface

Go to Download

A set of tools to query the GetCandy API, written in PHP

Go to Download

This bundle provides a flexible and convenient tool for building fetchXml queries.

Go to Download

A quick-and-dirty tool for converting raw MySQL query output to CSV.

Go to Download

Tool to log heavy database queries in the Laravel application

Go to Download

Zero-configuration drop-in tool to automatically optimize SQL queries issued through doctrine

Go to Download

Query Mail is a simple and powerful tools that generate fancy emails for reporting, statistics or monitoring your data.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download