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.

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

Performance generating SQL with more than a few tables is not great #50

Open
dmcghan opened this issue Feb 6, 2024 · 0 comments
Open

Comments

@dmcghan
Copy link

dmcghan commented Feb 6, 2024

I use Quick SQL in APEX where there's an editor on the left and the SQL output on the right. I was recently working on a new model that had 28 tables and ~300 total columns (~11 columns per table). The model had 36 ref constraints. While not small, this isn't a very large or complex schema.

It takes Quick SQL about 2 seconds to generate the SQL for this schema. While that may not seem like much, because it blocks the main event loop, it makes interactions with input fields difficult to manage and results in a bad user experience. APEX is using a debounce, but it's not sufficient to address the problem. Anything blocking the event loop for that long will result in a bad UX.

An async API to generate the SQL would fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant