# Nullables - why? and how?

**URL:** <https://discourse.julialang.org/t/nullables-why-and-how/7852>\
**Category:** New to Julia\
**Created:** [December 19, 2017, 4:26pm UTC](https://discourse.julialang.org/t/nullables-why-and-how/7852 "2017-12-19T16:26:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [December 19, 2017, 4:34pm UTC](https://discourse.julialang.org/t/nullables-why-and-how/7852/3 "2017-12-19T16:34:54Z")

</div>

You may find this useful:

> [@DataFrames 0.11 released](https://discourse.julialang.org/t/dataframes-0-11-released/7296):
>
> After a long and complex development period, we are glad to announce that version 0.11.0 of DataFrames has been released. Among other features listed in the [release notes](https://github.com/JuliaData/DataFrames.jl/releases/tag/v0.11.0), the major change introduced by this version is the move from the NA value (from the [DataArrays](https://github.com/JuliaStats/DataArrays.jl) package) to the new missing value (from the [Missings](https://github.com/JuliaData/Missings.jl) package, and [soon in Base](https://github.com/JuliaLang/julia/pull/24653)). DataFrames have been completely decoupled from DataArrays: the DataFrame constructor will no longer convert columns to DataArrays, but will keep them a…

---

_[View the full topic](https://discourse.julialang.org/t/nullables-why-and-how/7852)._