# Named query error "out of index"

**URL:** <https://forum.inductiveautomation.com/t/named-query-error-out-of-index/60615>\
**Category:** Ignition\
**Tags:** perspective, namedqueries, database, ignition80\
**Created:** [June 10, 2022, 2:16pm UTC](https://forum.inductiveautomation.com/t/named-query-error-out-of-index/60615 "2022-06-10T14:16:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [June 10, 2022, 2:29pm UTC](https://forum.inductiveautomation.com/t/named-query-error-out-of-index/60615/4 "2022-06-10T14:29:36Z")

</div>

Have you tried it as you posted it here or were you just condensing all of your tries into a single code block?

Named Queries do not handle comments well all of the time, especially if the comments include parameters.

> [@Comments in named queries?](https://forum.inductiveautomation.com/t/comments-in-named-queries/53709/2):
>
> Comments are fine, it’s just that our parser is (currently) too dumb to distinguish a commented parameter from a legitimate one, so: SELECT \* FROM TABLE WHERE A = :param --AND B = :param2 Should be fine, but is what currently throws an error, because the parser thinks it needs an additional value for param2.

Also, can you show the details of the error, preferably in a code block.

---

_[View the full topic](https://forum.inductiveautomation.com/t/named-query-error-out-of-index/60615)._