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

Support 'tables' based on parameterized queries #29

Closed
timotaularson opened this issue Oct 15, 2018 · 3 comments
Closed

Support 'tables' based on parameterized queries #29

timotaularson opened this issue Oct 15, 2018 · 3 comments

Comments

@timotaularson
Copy link

No description provided.

@nalimilan
Copy link
Member

Please be more specific.

@quinnj
Copy link
Member

quinnj commented Oct 15, 2018

Closing in favor of JuliaDatabases/ODBC.jl#210, since I think that's the real request.

@quinnj quinnj closed this as completed Oct 15, 2018
@timotaularson
Copy link
Author

While that was the motivating request, I opened this issue because I thought it would be generally useful for a 'table' source to be able to support parameters. I will be more specific as you requested.

The schema currently provides names and types, which are both column-level details.
There should also be a way to express table-level details.

Some examples include specifying the presence of or need for multi-column indexes, whether the table is persisted or ephemeral, most efficient access patterns (e.g. by row or by column, sequential or random), and my original use case of parameters in case the 'table' is not a direct representation of data but a view/query against a larger data source.

In each of these examples something of specific concern to a table interface is being expressed about the data which is stored in or accessed via the rows and columns, but the information is table-level and cannot be expressed well just at the column (name, type) level.

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

3 participants