Download the PHP
package greenlion/php-sql-parser without Composer
On this page you can find all versions of the php package
greenlion/php-sql-parser. It is possible to download/install
these versions without Composer. Possible dependencies are resolved
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.
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.
Full support for the MySQL dialect for the following statement types
Other SQL statement types
Other statements are returned as an array of tokens. This is not as structured as the information available about the above types. See the ParserManual for more information.
Other SQL dialects
Since the MySQL SQL dialect is very close to SQL-92, this should work for most database applications that need a SQL parser. If using another database dialect, then you may want to change the reserved words - see the ParserManual. It supports UNION, subqueries and compound statements.
The parser is a self contained class. It has no external dependencies. The parser uses a small amount of regex.
The focus of the parser is complete and accurate support for the MySQL SQL dialect. The focus is not on optimizing for performance. It is expected that you will present syntactically valid queries.