Everything I have ever seen in the Ignition documentation and in these forums says nothing of aliasing tables, schema names, and columns. In the past, I used the database names everywhere, but eventually there came times when I had to move a table to a different schema, rename a table, or rename a column. In these cases, I had to spend hours combing through the system to find and replace everything and then test everything to make sure I didn’t miss something somewhere.
Is there a best practice for handling this problem in Ignition? Is there a way to do it that will still allow me to use things like Named Queries with their built-in caching on the Gateway?
If there is not, I am leaning toward creating a DAL in my projects that defines all of this in one place and then creating all SQL code in scripts. The key downside to this approach at the moment is that I cannot use Named Queries and would have to down the same cache to every single client.