Hmm, this is very odd. I’m wondering if it’s not something in mySQL.
–I’m using Ignition 7.5.1. I just downloaded it from the main download page two days ago – so that one.
–The component calling the stored procedure is a dropdown box. It’s really not the component doing the reading. In the property change event handler for the dropdown box, we call a stored procedure to retrieve values from the database associated with the user’s selection. We then pass those values to tags.
call = system.db.createSProcCall(“sp_locationdpdwn”)
call.registerInParam(1, system.db.INTEGER, locationid)
rs = call.getResultSet()
results = system.dataset.toPyDataSet(rs)
for row in results:
location = locationid
uwi = row[“LSDdwn”]
pumptypeid = row[“pumptypeid”]
The procedure returns columns called LSDdwn, pumptypeid, and Name. Name is a rather generic word, so I aliased it in the stored procedure by calling it “ptName”, as in "SELECT pt.Name AS ptName ". If I change that last line to “system.tag.writeToTag(“Pressure/Pumptype”, row[“ptName”])” it throws an error message that says “Column name ‘ptName’ not found.”
– It happens in both the client and the designer.