Sameer Deshmukh

@info-rchitect yes I'm also for implementing this issue. Sorry I've been on vacation so couldn't read your comments properly previously. Regarding the code that you've posted, using the `where` clause...

Can you connect them with `and`? It can be something like: ``` df.where(df[:a].eq(3)).and(df[:b].eq(2)) ```

Yeah. You can see notebooks in the README as an example as of now too.

You can start a session with `rake pry` and then call `join` on your DataFrame like `df.join(....)`.

@Shekharrajak yes you can.

@gnilrets WDYT?

If I understand you correctly, you are basically proposing that parts of `join` should be included into `merge` right? Why is that? You can very well do the same thing...

Why should the default be changed from `:inner` to `:index`? Is there any compelling reason? > So we don't need to solve separate merge issue . What exactly do you...

Interesting use case. Don't think it's available as of now. @domitry maybe we can some file called `iruby_on_boot.rb` which is run every time a new notebook is created? User can...

Daru is currently using the default ruby CSV library (written in pure ruby) for reading CSV files so thats a botteneck we cant avoid. But there a bunch of options...