Skip to content

Ibis: creating columns, fixing bugs #302

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

Merged
merged 2 commits into from
Nov 12, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/reading.md
Original file line number Diff line number Diff line change
Expand Up @@ -676,7 +676,7 @@ canlang_table

Although it looks like we might have obtained the whole data frame from the database, we didn't!
It's a *reference*; the data is still stored only in the SQLite database. The `canlang_table` object
is an `AlchemyTable` (`ibis` is using `sqlalchemy` under the hood!), which, when printed, tells
is a `DatabaseTable`, which, when printed, tells
you which columns are available in the table. But unlike a usual `pandas` data frame,
we do not immediately know how many rows are in the table. In order to find out how many
rows there are, we have to send an SQL *query* (i.e., command) to the data base.
Expand Down Expand Up @@ -721,8 +721,8 @@ response for us. So `ibis` does all the hard work of translating from Python to
we can just stick with Python!

The `ibis` package provides lots of `pandas`-like tools for working with database tables.
For example, we can look at the first few rows of the table by using the `head` function---and
we won't forget to `execute` to see the result!
For example, we can look at the first few rows of the table by using the `head` function,
followed by `execute` to retrieve the response.

```{index} database; head, ibis;
```
Expand Down