# Table cannot have a number as name of a column

**URL:** <https://forum.inductiveautomation.com/t/table-cannot-have-a-number-as-name-of-a-column/74897>\
**Category:** Ignition\
**Created:** [June 12, 2023, 9:11am UTC](https://forum.inductiveautomation.com/t/table-cannot-have-a-number-as-name-of-a-column/74897 "2023-06-12T09:11:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\
**Post date:** [June 12, 2023, 12:54pm UTC](https://forum.inductiveautomation.com/t/table-cannot-have-a-number-as-name-of-a-column/74897/5 "2023-06-12T12:54:43Z")

</div>

I see there are several workarounds but using an Expressions is not ideal for us because we try to use Python for our Business Logic and using alternate names for the columns means more transformations in the process from the original query.  
There's a similar problem for dictionaries associated to a binding which I notified before but hasn't been replied to:

> [@\[BUG\]: binding returning a dict with string keys representing a number cause KeyError in designer](https://forum.inductiveautomation.com/t/bug-binding-returning-a-dict-with-string-keys-representing-a-number-cause-keyerror-in-designer/74619):
>
> If you create a binding which returns a dictionary and some keys are strings that represent a number they are interpreted as a number which is not a valid key for the dict. See screenshot below (0 is a string "0" but is interpreted nevertheless as the number 0). At the moment only solution is to prepend a "\_0" to the keys. [image] [image]

hope these will be properly addressed in the future.

---

_[View the full topic](https://forum.inductiveautomation.com/t/table-cannot-have-a-number-as-name-of-a-column/74897)._