You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
SQL Error where too many samples are selected
To Reproduce
Steps to reproduce the behavior, for example:
Select multiple samples in Validation plugin (or a big database?)
Apply a filter
See error:
"Operational Error: too many FROM clause terms, max 200"
Expected behavior
SQL query ok, no bug.
Probably LEFT/INNER JOIN problem.
Find a way to deal with multiple samples at the time.
See if using Sources solve the problem.
The text was updated successfully, but these errors were encountered:
I agree for a maximum number of fields, on variant view.
However, we will probably use CuteVariant to explore statistically, or with deep learning, and in that way, we will probably need to select a large number of information (fields) for a large number of samples (LEFT JOIN)
Dealing with more than 200 samples in a VQL query (e.g. WHERE samples.$any.gt >=0) is impossible.
But a plugin specific for statistical questions using specific SQL queries is possible.
An idea should be to reduce the number of considered samples to those on the "basket" (cf Validation plugin)
- Add 'selected_samples' state to prevent Genotype based queries from failing due to too many SQLite clause terms
- Pass it to querybuilder
- Log message instead of letting the unrecoverable error occur
- Fix group by widget related issues
- Fix report related issues
- Update tests
Describe the bug
SQL Error where too many samples are selected
To Reproduce
Steps to reproduce the behavior, for example:
Expected behavior
SQL query ok, no bug.
Probably LEFT/INNER JOIN problem.
Find a way to deal with multiple samples at the time.
See if using Sources solve the problem.
The text was updated successfully, but these errors were encountered: