# Is the update quota too restrictive for more than a prototype?

**URL:** https://community.glideapps.com/t/is-the-update-quota-too-restrictive-for-more-than-a-prototype/61248
**Category:** Ask for Help
**Created:** [May 2, 2023, 10:02am UTC](https://community.glideapps.com/t/is-the-update-quota-too-restrictive-for-more-than-a-prototype/61248 "2023-05-02T10:02:14Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)
#### Post date: [May 2, 2023, 1:50pm UTC](https://community.glideapps.com/t/is-the-update-quota-too-restrictive-for-more-than-a-prototype/61248/4 "2023-05-02T13:50:30Z")

</div>

> [@Xavier\_Delplanque](#):
>
> Maybe, a solution would be to have some kind of “local variables” which wouldn’t count against the quota but wouldn’t be saved in the database.

Many people agree with you about the updates, and this _is_ the solution, or at least partially so.

Vote HERE:

> [@Session Variable Column](https://community.glideapps.com/t/session-variable-column/40260):
>
> I’ve always thought that it’s really useful how user specific columns only store values locally and for the duration of your session while you are not signed in. This allows for those column values to “reset” after you close the app, and the data does not need to be sent and synchronized with glide servers. However, once you sign in, then those values are sent to, and stored, on Glide’s servers. I think a new Session column type could be really useful. It would work just like user specific c…

---

_[View the full topic](https://community.glideapps.com/t/is-the-update-quota-too-restrictive-for-more-than-a-prototype/61248)._