Libraries tagged by create table

cakesol/filter

0 Favers
24 Downloads

Create filters which take care for frontend filtering and add the filter to the entity table filter

Go to Download


astamatech/laravel-autoseed

0 Favers
5 Downloads

A tool for retrieving data from a table in a database and inputting it into a seeder file in a Laravel-based application. The goal is to make it easier for developers to create seeders so they don't write manually.

Go to Download


adnen/php-crud-with-cli

0 Favers
0 Downloads

This is a simple PHP CLI application that performs basic CRUD (Create, Read, Update, Delete) operations on a user table in a MySQL database using PDO (PHP Data Objects). The script interacts with the database through a Command-Line Interface (CLI) and outputs results as JSON in the terminal.

Go to Download


sprov03/laravel-code-generator

1 Favers
1135 Downloads

Generator Temperated Code form database tables. This Package provides data to templates that you create to generate code to scaffold projects rapidly so you can spend most of your time doing the fun stuff.

Go to Download


mhinspeya/mhinspeya-employee-core

0 Favers
0 Downloads

The 'Modehaus Employee' module for Magento enables retail organizations to spotlight their employees, fostering a sense of community and trust among customers. This module provides a dedicated space within the Magento store where businesses can feature profiles of their team members, including their roles, expertise, and personal backgrounds. Key Features: 1. Employee Profiles: Create comprehensive profiles for each team member, including their name, position, bio, and a photo. 2. Role-Based Filtering: Allow customers to filter employees based on their roles or departments within the organization. 3. Customizable Templates: Customize the layout and design of employee profiles to match the branding and aesthetics of your store. 4. Social Integration: Optionally include links to employees' social media profiles to encourage engagement and connection. 5. SEO-Friendly: Ensure that employee profiles are optimized for search engines, helping to improve visibility and attract organic traffic. 6. Easy Management: Easily add, edit, or remove employee profiles through a user-friendly interface within the Magento admin panel. 7. Responsive Design: Ensure a seamless browsing experience for customers on all devices, including desktops, tablets, and smartphones. With the 'Modehaus Employee' module, retailers can humanize their brand and build stronger relationships with customers by highlighting the talented individuals who contribute to their success.

Go to Download


mhinspeya/mhinspeya-employee

0 Favers
5 Downloads

The 'Modehaus Employee' module for Magento enables retail organizations to spotlight their employees, fostering a sense of community and trust among customers. This module provides a dedicated space within the Magento store where businesses can feature profiles of their team members, including their roles, expertise, and personal backgrounds. Key Features: 1. Employee Profiles: Create comprehensive profiles for each team member, including their name, position, bio, and a photo. 2. Role-Based Filtering: Allow customers to filter employees based on their roles or departments within the organization. 3. Customizable Templates: Customize the layout and design of employee profiles to match the branding and aesthetics of your store. 4. Social Integration: Optionally include links to employees' social media profiles to encourage engagement and connection. 5. SEO-Friendly: Ensure that employee profiles are optimized for search engines, helping to improve visibility and attract organic traffic. 6. Easy Management: Easily add, edit, or remove employee profiles through a user-friendly interface within the Magento admin panel. 7. Responsive Design: Ensure a seamless browsing experience for customers on all devices, including desktops, tablets, and smartphones. With the 'Modehaus Employee' module, retailers can humanize their brand and build stronger relationships with customers by highlighting the talented individuals who contribute to their success.

Go to Download


lichtner/fluentpdo

929 Favers
294043 Downloads

FluentPDO is a quick and light PHP library for rapid query building. It features a smart join builder, which automatically creates table joins.

Go to Download


envms/fluentpdo

924 Favers
556865 Downloads

FluentPDO is a quick and light PHP library for rapid query building. It features a smart join builder, which automatically creates table joins.

Go to Download


fpdo/fluentpdo

923 Favers
252960 Downloads

FluentPDO is a quick and light PHP library for rapid query building. It features a smart join builder, which automatically creates table joins.

Go to Download


starcitizentools/tabber-neue

23 Favers
7067 Downloads

Allows to create tabs within a page. Forked from Extension:Tabber

Go to Download


repat/laravel-job-models

8 Favers
28769 Downloads

Eloquent Models for the tables job and job_fails as created by artisan queue:table and queue:failed-table

Go to Download


level-2/maphper

54 Favers
768 Downloads

A lightweight ORM using the DataMapper pattern, creates database tables on the fly.

Go to Download


brunogritti/laravel-user-activity-logs

0 Favers
513 Downloads

Creates a laravel table, model and trait that logs all user activity based on which model it's imported

Go to Download


otifsolutions/laravel-settings

1 Favers
4470 Downloads

This package creates a complete generic Settings Table and structure to be used in project. For Laravel.

Go to Download


nogrod/tyre24-seller-php-sdk

1 Favers
469 Downloads

## API Versioning We're constantly updating and improving the API, and while we try to ensure backwards compatibility, there's always a chance that we'll introduce a change that affects the way your app works. To get around any problems that this might cause, we recommend that you include the Accept header with every API request that you make. This header enables you to target your request to a particular version of the API. It looks like this in HTTP: ```text Accept: application/vnd.saitowag.api+json;version={version_number} ``` Normally, you set the value of the placeholder to the current version of the API. But if you're troubleshooting your app, and you know that an older version of the API works perfectly, say version 1.0, you'd substitute 1.0 for the placeholder value. The API then handles the request as if it were for version 1.0, and your app goes back to working properly. ### Example of an error with invalid `ACCEPT` header. The `HTTP status code` in case of an invalid `ACCEPT` header will be `400 Bad Request` and the following response will be returned. ```json { "data": [ { "error_code": "ERR_ACCEPT_HEADER_NOT_VALID", "error_message": "Accept header is not valid or not set." } ] } ``` ### Unexpected Error If an unexpected error occours, a so called Error General will be returned. The `HTTP status code` in case of an invalid `ACCEPT` header will be `500` and the following response will be returned. ```json { "data": [ { "error_code": "ERR_GENERAL", "error_message": "An unexpected error has occurred. If this problem persists, please contact our support." } ] } ``` ### Invalid Endpoint Error Any call to a non-existing API endpoint (i.e. wrong route) will return a response with `HTTP status code` `404` and the following response body: ```json { "data": [ { "error_code": "ERR_GENERAL_INVALID_ENDPOINT", "error_message": "The requested endpoint does not exist." } ] } ``` Please, note that this error is returned also when a request parameter, part of a valid route, is not well formed. For example, a call to a route that contains a wrong order id (i.e. it does not meet the accepted order id pattern - e.g. 123456789PAC instead of PAC123456789) will return the error just mentioned, as the route is considered as badly formed. In conclusion, please pay special attention to all those routes that have request parameters with specific pattern requirements. ### Shipping Method IDs These ids may not be available in all the countries. | ID | Name | | --- | --- | | 1 | Standard `Standard` | | 2 | Self-collection `Selbstabholung` | | 3 | Express morning (truck) `Express-Morgen (LKW)` | | 4 | Express Today (Truck) `Express-Heute (LKW)` | | 5 | Express morning (package forwarding) `Express-Morgen (Packet Spedition)` | | 7 | Express-now | ### Payment Method IDs These ids may not be available in all the countries. | ID | Name | | --- | --- | | 1 | SEPA Direct Debit `SEPA-Lastschrift` | | 2 | Prepayment `Vorkasse` | | 3 | Cash on delivery `Nachnahme` | | 4 | PayPal/Credit Card `PayPal/Kreditkarte` | | 5 | open payment method `offene Zahlungsart` | | 7 | Invoice(8 days payment term) `Rechnung(8 Tage Zahlungsziel)` | | 8 | open payment method (SEPA) `offene Zahlungsart (SEPA)` | ## Query String Filters Query String Filters | Operator | Full Name | Description | Example | | ------ | ------ | ------ | ------ | | eq | Equal | Used to narrow down the result of a query to some specific value, for specified field. It adds the "**=**" symbol to the SQL query. Eg. `{url}?filter[{alias_name}]=eq;11` will result in the following sql: `SELECT {field_name} AS {alias_name} FROM {table_name} WHERE {alias_name} = 11` | integer: `{url}?filter[id]=eq;21`float: `{url}?filter[average]=eq;3.7`string: `{url}?filter[free_text]=eq;apple`Date: `{url}?filter[birthday]=eq;2020-06-03`DateTime: `{url}?filter[created_at]=eq;2020-06-03 14:32:32`boolean: `{url}?filter[is_active]=eq;1` | | neq | Not equal | Used to exclude the value from a query result. It adds the "****" symbol to the SQL query. Eg. `{url}?filter[{alias_name}]=neq;11` will result in the following sql: `SELECT {field_name} AS {alias_name} FROM {table_name} WHERE {alias_name} 11` | integer: `{url}?filter[id]=neq;21`float: `{url}?filter[average]=neq;3.7`string: `{url}?filter[free_text]=neq;apple`Date: `{url}?filter[birthday]=neq;2020-06-03`DateTime: `{url}?filter[created_at]=neq;2020-06-03 14:32:32`boolean: `{url}?filter[is_active]=neq;1` | | gt | Greater than | Used to reduce fetched values to those greater than the one provided in a query string. It adds the "**>**" symbol to the SQL query. Eg. `{url}?filter[{alias_name}]=gt;11` will result in the following sql: `SELECT {field_name} AS {alias_name} FROM {table_name} WHERE {alias_name} > 11` | integer: `{url}?filter[id]=gt;21`float: `{url}?filter[average]=gt;3.7`Date: `{url}?filter[birthday]=gt;2020-06-03`DateTime: `{url}?filter[created_at]=gt;2020-06-03 14:32:32` | | gte | Greater than or equal | Used to reduce fetched values to those greater than or equal to the one provided in a query string. It adds the "**>=**" symbol to the SQL query. Eg. `{url}?filter[{alias_name}]=gte;11` will result in the following sql: `SELECT {field_name} AS {alias_name} FROM {table_name} WHERE {alias_name} >= 11` | integer: `{url}?filter[id]=gte;21`float: `{url}?filter[average]=gte;3.7`Date: `{url}?filter[birthday]=gte;2020-06-03`DateTime: `{url}?filter[created_at]=gte;2020-06-03 14:32:32` | | lt | Less than | Used to reduce fetched values to those less than provided in a query string. It adds the "**

Go to Download


<< Previous Next >>