# Building a solver (Getting variable types)

**URL:** <https://discourse.julialang.org/t/building-a-solver-getting-variable-types/6587>\
**Category:** Optimization (Mathematical)\
**Tags:** question\
**Created:** [October 20, 2017, 6:49pm UTC](https://discourse.julialang.org/t/building-a-solver-getting-variable-types/6587 "2017-10-20T18:49:54Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![miles.lubin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/miles.lubin/32/279_2.png) [@miles.lubin](https://discourse.julialang.org/u/miles.lubin)\
**Post date:** [October 21, 2017, 12:18am UTC](https://discourse.julialang.org/t/building-a-solver-getting-variable-types/6587/8 "2017-10-21T00:18:40Z")

</div>

JuMP will call `setvartype!` on the MPB model after `loadproblem!` if there are any non-continuous variables.

You should be aware that MPB will soon be replaced and unsuported in Julia 0.7 and JuMP 0.19 in favor of MathOptInterface ([announcement](https://discourse.julialang.org/t/mathoptinterface-and-upcoming-breaking-changes-in-jump-0-19/4874)). We’re getting closer to having basic MOI functionality working on the JuMP side and solver interfaces, but it’s not quite usable yet.

---

_[View the full topic](https://discourse.julialang.org/t/building-a-solver-getting-variable-types/6587)._