Skip to content

SQLTables: "TABLE" vs "BASE TABLE" #235

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
Closed
bpintea opened this issue Mar 30, 2020 · 2 comments
Closed

SQLTables: "TABLE" vs "BASE TABLE" #235

bpintea opened this issue Mar 30, 2020 · 2 comments

Comments

@bpintea
Copy link
Collaborator

bpintea commented Mar 30, 2020

Some applications expect the non-alias & co tables to be of type TABLE, while others BASE TABLE and ignore the present entires if they don't conform to the expectation. This doesn't seem to be related to the release of the ODBC API the application is conforming to. We need a way to enable both types of applications to work.

Note that this concerns most often the listing of available tables and does't impede the execution of queries against those "missing" tables.
@bpintea
Copy link
Collaborator Author

bpintea commented Mar 30, 2020

The issue tracks the problem, the fix might be more suitable on the server.

@bpintea
Copy link
Collaborator Author

bpintea commented Apr 3, 2020

This issue needs to be solved in ES: elastic/elasticsearch#54671.

@bpintea bpintea closed this as completed Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bpintea