# Empty constraint

**URL:** <https://discourse.julialang.org/t/empty-constraint/4111>\
**Category:** Optimization (Mathematical)\
**Created:** [June 6, 2017, 3:04pm UTC](https://discourse.julialang.org/t/empty-constraint/4111 "2017-06-06T15:04:53Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mposs](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mposs/32/21087_2.png) [@mposs](https://discourse.julialang.org/u/mposs)\
**Post date:** [June 6, 2017, 7:56pm UTC](https://discourse.julialang.org/t/empty-constraint/4111/5 "2017-06-06T19:56:20Z")

</div>

That would not help me because I need to have references for my generated constraints and variables, and I can of course not use a new name at each iteration of my algorithm.

I think I can handle my specific algorithm by increasing the dimension of the “constraint array” on demand using the trick mentioned [here](https://discourse.julialang.org/t/dynamic-generation-of-constraints/4107/2). However, there does not seem to be a similar way to increase the size of the “variables array” dynamically. While I don’t need it for my current application, this seems to be a severe limitation of JuMP when compared to solvers classical APIs.

---

_[View the full topic](https://discourse.julialang.org/t/empty-constraint/4111)._