-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions? Feedback? #1
Comments
Just wanted to say that this looks awesome. Not sure we will use it given its early stage though. |
Hi, this project looks amazing. Is it possible to use this for validating plain SQL and not postgres sql? |
Since Postgres' SQL dialect is just a superset of "vanilla" SQL, there should be no problem validating that 👍 I guess the only risk would be to use something too fancy that postgres/postguard understand and accept, but your non-postgres database (sqlite for instance) does not. |
This looks super cool. The thing that would make it perfect, from my point of view, would be if you could point it at an actual postgres schema definition (i.e. a directory containing .sql files) as the source of truth for the database, rather than defining it with |
@gregplaysguitar Yeah, that would be great! Shouldn't be too hard either, now as I think about it… Just not sure if I will have time to work on it anytime soon. I've been sick for the last week and a half and stuff is already piling up 😉 |
@andywer do you have any pointers as to where to start with that? I'd love to help out, although I don't have much free time either... |
@gregplaysguitar You can have a look at:
I think the best way to get started with the |
Great, thanks! I’ve been wanting to dig into pg query parsing for another project too so keen to have a look at this. I’ll let you know how I go! |
Can it validate queries at runtime? |
No, it's build-time-only 😉 @LifeIsStrange |
that's unfortunate :) |
Add your feedback as a comment to this issue 📋
The text was updated successfully, but these errors were encountered: