Quick Start¶
Get up and running with General SQL Parser in just a few minutes! This guide will walk you through installation, basic setup, and your first SQL parsing example.
Prerequisites¶
- Java 8 or higher (Java 11+ recommended)
- Maven or Gradle for dependency management
- IDE (IntelliJ IDEA, Eclipse, or VS Code recommended)
Installation¶
Maven¶
Add the General SQL Parser dependency to your pom.xml
:
1 2 3 4 5 |
|
Gradle¶
Add the dependency to your build.gradle
:
1 |
|
Manual Installation¶
- Download the JAR file from our website
- Add it to your project's classpath
- Include any required dependencies
Your First SQL Parser¶
Let's create a simple example that parses a SQL statement:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
|
Expected Output¶
1 2 3 |
|
Database Vendor Support¶
General SQL Parser supports 30+ database vendors. Here are some common examples:
1 2 |
|
1 2 |
|
1 2 |
|
1 2 |
|
1 2 |
|
Common Use Cases¶
1. SQL Validation¶
1 2 3 4 5 |
|
2. Extract Table Names¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
|
3. Format SQL¶
1 2 3 4 5 6 7 8 9 10 |
|
Error Handling¶
Always handle parsing errors gracefully:
1 2 3 4 5 6 7 8 9 10 11 |
|
Next Steps¶
Now that you have General SQL Parser running, explore these areas:
Continue Learning
- Getting Started with GSP - Comprehensive tutorial
- Basic SQL Parsing - Learn parsing fundamentals
- Working with Different Databases - Multi-vendor support
- Performance Optimization - Speed up your parsing
- Error Handling - Robust error management
- Parse Oracle PL/SQL - Advanced Oracle features
- API Documentation - Complete API reference
- SQL Syntax Support - Supported SQL features
- Configuration Options - Parser configuration
Troubleshooting¶
Common Issues¶
Parse Error: Unexpected token
Solution: Check that you're using the correct database vendor. SQL syntax varies between databases.
1 2 3 4 5 6 7 |
|
ClassNotFoundException
Solution: Ensure the GSQLParser JAR is in your classpath and all dependencies are included.
OutOfMemoryError
Solution: For large SQL files, consider parsing statements individually or increase JVM heap size.
Getting Help¶
- 📖 Check our FAQ for common questions
- 💬 Visit our Support page for community help
- 📧 Contact technical support for commercial licenses
Ready for more advanced features? Continue with our comprehensive tutorials or explore specific how-to guides.