# Issue with DataFrames, operations on DataFrames now return Nullable Arrays?

**URL:** https://discourse.julialang.org/t/issue-with-dataframes-operations-on-dataframes-now-return-nullable-arrays/4946
**Category:** General Usage
**Created:** [July 19, 2017, 8:16am UTC](https://discourse.julialang.org/t/issue-with-dataframes-operations-on-dataframes-now-return-nullable-arrays/4946 "2017-07-19T08:16:40Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![ValdarT](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/valdart/32/24146_2.png) [@ValdarT](https://discourse.julialang.org/u/ValdarT)
#### Post date: [July 19, 2017, 10:35am UTC](https://discourse.julialang.org/t/issue-with-dataframes-operations-on-dataframes-now-return-nullable-arrays/4946/5 "2017-07-19T10:35:13Z")

</div>

CSV, ODBC and other packages built on top of DataStreams currently use Nullable to handle missing values. This is different from the NA/DataArray approach that DataFrames uses by default. But it is still a DataFrame.  
All this is unfortunate but it is being actively worked on. By Julia 0.7 all the packages should use a new approach that will be easier to work with - see [this announcement](https://discourse.julialang.org/t/announcement-an-update-on-dataframes-future-plans/4646).

In the meantime you can use DataTables that works more naturally with the Nullable data type or convert things manually.

---

_[View the full topic](https://discourse.julialang.org/t/issue-with-dataframes-operations-on-dataframes-now-return-nullable-arrays/4946)._