# Are comments in Named Queries known to not work correctly?

**URL:** <https://forum.inductiveautomation.com/t/are-comments-in-named-queries-known-to-not-work-correctly/79319>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [September 19, 2023, 1:13am UTC](https://forum.inductiveautomation.com/t/are-comments-in-named-queries-known-to-not-work-correctly/79319 "2023-09-19T01:13:02Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 19, 2023, 11:36am UTC](https://forum.inductiveautomation.com/t/are-comments-in-named-queries-known-to-not-work-correctly/79319/11 "2023-09-19T11:36:41Z")

</div>

> [@Kevin.Herron](#):
>
> it's a JDBC limitation.

This. Comments are part of SQL **scripting** , not SQL **statements**. Scripting is outside the scope of JDBC, and is only partially supported by some JDBC drivers.

This is complicated in named queries by Ignition's need to find parameter references and place question marks in the right places (value params), and/or perform string interpolation (queryString params). JDBC itself only accepts question-mark parameters.

Sorry.

---

_[View the full topic](https://forum.inductiveautomation.com/t/are-comments-in-named-queries-known-to-not-work-correctly/79319)._