# Queryverse queries lose type information?

**URL:** https://discourse.julialang.org/t/queryverse-queries-lose-type-information/40572
**Category:** General Usage
**Tags:** queryverse
**Created:** [June 1, 2020, 6:03pm UTC](https://discourse.julialang.org/t/queryverse-queries-lose-type-information/40572 "2020-06-01T18:03:50Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![dlakelan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dlakelan/32/8491_2.png) [@dlakelan](https://discourse.julialang.org/u/dlakelan)
#### Post date: [June 1, 2020, 9:17pm UTC](https://discourse.julialang.org/t/queryverse-queries-lose-type-information/40572/9 "2020-06-01T21:17:47Z")

</div>

I have a suspicion that tryparse, which can return all kinds of data types, might be forcing a conversion to DataValue{Any}. I’ll see if I can make that type-stable and see what results.

learning … learning…

Indeed:

```julia
dflong2 = DataFrame(dflong |> @mutate(year = something(tryparse(Int,string(_.variable)[end-3:end]),0)))
display(first(dflong2,10))

```

gives a table with proper data types.

In this case it’s OK to encode meaningless data as 0. But I find it weird that I lose ALL type info rather than just the particular column “year”.

---

_[View the full topic](https://discourse.julialang.org/t/queryverse-queries-lose-type-information/40572)._