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

Return value of execute and sql_execute should be documented #578

Open
jar600 opened this issue Aug 30, 2017 · 2 comments
Open

Return value of execute and sql_execute should be documented #578

jar600 opened this issue Aug 30, 2017 · 2 comments

Comments

@jar600
Copy link
Contributor

jar600 commented Aug 30, 2017

The API documentation says execute returns a cursor, but doesn't say what a cursor is or what its methods are or give a hyperlink to outside documentation.

Similarly, for sql_execute, nothing at all is said about the return value. (I gather the result is a pandas.DataFrame, but the documentation should say so.)

This makes it hard (impossible) to figure out how to access a table from python, which would seem to be a primary use case for the API.

Some examples of doing SELECT through the API would be nice.

@riastradh-probcomp
Copy link
Contributor

riastradh-probcomp commented Aug 30, 2017 via email

@jar600
Copy link
Contributor Author

jar600 commented Aug 30, 2017

Thanks. I think I've figured out what I need to know for my own purposes. The issue is specifically about the documentation, by which I mean the 'Bayeslite API reference' currently on the web at http://probcomp.csail.mit.edu/bayesdb/doc/api.html, not a request for information for me in particular.

I don't think I'll have time to fix this, but if there's any interest in having people outside the project be able to use the API using the documentation as their guide (as opposed to reading source code), without the advantage I have of being able to ask questions of human beings, then I recommend that the documentation be improved, at least in this particular way.

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

2 participants