Libraries tagged by query generator
brokerexchange/elasticbuilder
1067 Downloads
Query Builder for Elasticsearch.
peterzaccha/jo-query-generator
122 Downloads
A Laravel Package
mvbsoft/yii2-query-manager
37 Downloads
A query generator that allows visually generating a query to a MongoDB or PostgreSQL database using a frontend. Additionally, it provides the ability to use the generated queries for PHP arrays.
hooshid/laravel-query-maker
44 Downloads
A Elegant Query Maker
code-mine/zf-tactician-comandquery-generator
6050 Downloads
Command Query generator for tactician lib
aymanelarian/import-query-generator-pg
5 Downloads
An efficient Postgres query generator for mass resource import, distinguishing between new records and records to update.
saxulum/saxulum-elasticsearch-querybuilder-generator
9 Downloads
A query builder generator for elasticsearch
ruhulfbr/csv-to-query
1 Downloads
This package provides a simple utility to convert data from a CSV file into SQL queries for database insertion and Create table.
fattureincloud/pt-command-generator
1 Downloads
Generates pt-online-schema-change commands for MySQL, given the ALTER TABLE query
dabl/generator
219 Downloads
DABL ORM code generator
mxneyio/php-graphql-oqm
372 Downloads
GraphQL Object-to-Query Mapper (QOM) which generates objects from API schema
dreamblazenet/gensql
22 Downloads
Simple SQL-Query Generator
tslol/docker-api-php
2 Downloads
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..." } ```
sypherlev/architect
169 Downloads
Data class generator for sypherlev/blueprint
rogergerecke/shopware-6-php-swagger-client
0 Downloads
This endpoint reference contains an overview of all endpoints comprising the Shopware Admin API. For a better overview, all CRUD-endpoints are hidden by default. If you want to show also CRUD-endpoints add the query parameter `type=jsonapi`.