Skip to content

Improve parser errors #138

@elliotchance

Description

@elliotchance

Parser errors should be way more friendly, they should at least:

  1. Describe the exact position (line/column number)
  2. Show more surrounding tokens or the whole line so its much easier to understand where the error is.
  3. Provide helpful tips for common misconceptions. For example, inline PRIMARY KEY should provide a link to the doc with a example rather than just say "error at PRIMARY"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions