Weave Code
Datatable Laravel Package
openskill/datatable
OpenSkill Datatable is a Laravel package for building server-side data tables from Eloquent or query builder sources, with column formatting, search, sorting, filtering, pagination, and AJAX-ready responses for flexible admin interfaces.
Modular server side Datatable package for Laravel 5 for various client side table plugins
Frequently asked questions about Datatable
- Does openskill/datatable support Laravel 8, 9, 10, or 11?
- No. The package targets Laravel 5.0 through 5.2 and uses PHP 5.5/5.6-era idioms. Every Laravel version it supports has been end-of-life for years. On Laravel 6 and newer, treat the package as a reference implementation rather than a drop-in dependency.
- How do I install openskill/datatable in a Laravel project?
- Composer-level installation is trivial in principle, but the package predates Laravel 5.5 package auto-discovery. You must manually register the service provider and facade alias in config/app.php. In practice, installation only makes sense on a Laravel 5.x application that already matches the package's supported stack.
- Is openskill/datatable safe to use in production?
- Treat it as high risk. The package has had no release since January 2016, so you inherit the full security-patch burden. Any package that accepts client-supplied column names and turns them into orderBy or whereRaw calls deserves a security review before production use. Verify identifier whitelisting and parameter binding explicitly.
- How does openskill/datatable handle server-side search, sorting, and pagination?
- It translates the query-string protocol emitted by client-side table plugins into an Eloquent or Query Builder query. Parameters such as draw, start, length, order, search, and columns drive the query and the JSON response envelope. The package is an edge-layer adapter, not a domain component, so isolate it from your domain model.
- Can openskill/datatable work with DataTables and other client-side table plugins?
- The package's main architectural idea is a driver or strategy layer that lets one server-side contract serve multiple front-end table plugins. That abstraction is genuinely useful, but it is also the part most likely to have drifted from current plugin protocols. Pin your front-end plugin version and verify that its current release still speaks the protocol this package emits.
- Does openskill/datatable support Eloquent relationships and joins without N+1 queries?
- The package builds from Eloquent or Query Builder sources, but the provided context does not document how it handles relations or joins in server-side search and sort. You must verify whether it avoids N+1 queries and Cartesian blowups with your actual schema. Test this explicitly before relying on it for complex admin tables.
- How do I port openskill/datatable to Laravel 9 or Laravel 10?
- This is not a port; it is a rewrite with the package as a specification. Spend a day reading the source to extract the request-parameter schema, the response envelope, and the driver abstraction. Then build a thin internal adapter of roughly 200 to 400 lines on your current framework version with your own authorization hooks and tests.
- Is openskill/datatable still maintained?
- No evidence suggests active maintenance. The last release was 2016-01-18, the repository has roughly 52 stars, and there is no maintained branch. If you have an existing Laravel 5 application already using it, vendor the source in-repo or under a private VCS fork and treat it as first-party code.
- How should I handle authorization and per-tenant row scoping with openskill/datatable?
- Inject a base query builder that already applies your authorization and tenant scoping. Then verify that the package respects that base query in its count query as well as its data query. Do not rely on the package to enforce row-level access on its own.
- What are the alternatives to openskill/datatable for Laravel server-side data tables?
- For a maintained Laravel stack, consider a package that explicitly supports your current Laravel and PHP versions, or implement the request and response contract directly against your client-side plugin's documented server-side protocol. The fallback is a small internal adapter, typically a few hundred lines. That approach keeps the good architectural idea without inheriting an abandoned dependency.
Weaver
How can I help you explore Laravel packages today?