immutable

• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect

Here is what I've noticed:

• ipfs.block.get
  • docs say it returns a Block, but it returns a Uint8Array
  • docs are missing the preload option
• ipfs.block.put
  • docs say it can also take a Block as a parameter, but it can only be a Uint8Array
  • docs say it can take a cid as an option, but the implementation ignores such a parameter
  • docs say it returns a Block, b

Is your feature request related to a problem? Please describe.
CSV files produced in different locales have different default separators, a comma-separated file (",") is but one type of CSV.

In Sweden we usually use a semicolon (";") as separator and many CSV files use a tab as separator ("\t"). Importing CSVs requires reformatting them before import, and causes inoperability issues and f

Currently they wrap them into pvector which is not as efficient as it could be in Python 3.

This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:

• http/README.md has no tutorial on how to try out ipfs-http
• ipfs-http supports only `i

This operations will be used to drop elements in the steam on the right of the given element

var elements = []int{10,12,7,41,5,6}
res:=koazee.StreamOf(elements).DropRight(12).Out().Val()
fmt.Println(res)

// [10,12]