Skip to content

REQ: Examples for documentation #13

@spazm

Description

@spazm

I like the README. I think it would be improved by adding a specific use case to make it feel less abstract to a potential new user. Something like a SYNOPSIS section in a man page or perldoc.

Ideas for what would make a good example?

  1. an example query where a dba might ask to change the query to improve query plan or similar, or change a join order. Then we could show breaking that down with named bindings, maybe splitting the subquery into it's own testable import?

I don't have the context, but I'm sure this a query or two that you've had to clean up (especially deep in the billing code!).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions