Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: use upstream node-sql-parser package #70

Merged
merged 3 commits into from
Dec 11, 2023
Merged

fix: use upstream node-sql-parser package #70

merged 3 commits into from
Dec 11, 2023

Commits on Dec 11, 2023

  1. fix: use upstream node-sql-parser package 

    This changes Yates to use the original upstream node-sql-parser package.
The only reason Yates uses my fork is because at the time the
`exprToSQL` method I contributed was not available in the general
release. Fast-forward to 10 months later and my fork is now 499 commits
behind master XD
The only real difference that has to be made is the way that `$n`
parameters are represented in the AST, but this is a simple change to
make.

Signed-off-by: Lucian Buzzo <lucian.buzzo@gmail.com>
    @LucianBuzzo
    LucianBuzzo committed Dec 11, 2023
    Configuration menu
    Copy the full SHA
    cdb1d88 View commit details
    Browse the repository at this point in the history

  2. fix: update to work with latest prisma client version 

    Signed-off-by: Lucian Buzzo <lucian.buzzo@gmail.com>
    @LucianBuzzo
    LucianBuzzo committed Dec 11, 2023
    Configuration menu
    Copy the full SHA
    a6da0ab View commit details
    Browse the repository at this point in the history

  3. chore: cleanup imports in expression file 

    Signed-off-by: Lucian Buzzo <lucian.buzzo@gmail.com>
    @LucianBuzzo
    LucianBuzzo committed Dec 11, 2023
    Configuration menu
    Copy the full SHA
    91779eb View commit details
    Browse the repository at this point in the history