-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unexpected EOF / segfault #349
Comments
@kaidaguerre this might be an interesting clue?
|
Workaround: build the query string in a prior CTE.
|
@kaidaguerre Here is a variation. In this example the happy path looks like:
The sad path:
If you look at the output of the prompts CTE it's the same in both cases, but doing them in sequence is a fail, the workaround is to produce the prompts using a CTE that embeds another CTE, vs a chain of 2 CTEs. happy path
sad path
|
One more example, @kaidaguerre. A common feature of these examples: the input to the join is a value constructed by string concatenation. Seems like I always wind up doing a nested-CTE workaround in such cases in order to avoid the EOF fail.
|
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
These are seemingly identical.
But one of these is not like the other. At least the crash produces a spew of entrails that hopefully will help.
Logs: https://gist.github.com/judell/60a13d7f848ba08adc2dd1c6b8748bc8
The text was updated successfully, but these errors were encountered: