Issues
2 of 2
MySQL query is simply being ignored after failing after MariaDB 10.4 server start.
Closed
Description
Environment
Windows 10 Home
IIS 10.5
MariaDB 10.4
Details
Assignee
Pothys - MitrahSoftPothys - MitrahSoftReporter
Bradley HicksBradley HicksPriority
NewLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Pothys - MitrahSoft
Pothys - MitrahSoftReporter
Bradley Hicks
Bradley HicksPriority
Labels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created 13 January 2021 at 22:15
Updated 18 January 2021 at 15:06
Resolved 18 January 2021 at 15:06
Activity
Pothys - MitrahSoft18 January 2021 at 15:05
As the reporter said I close this ticket. If this error comes in the future means I will reopen this ticket
Bradley Hicks14 January 2021 at 04:25
Please close this. I traced this to an apparent issue with a process nested in CFTransaction
I have a call to a function that contains a query. The function fires at every step, as debug messages will let me know, but the query is not firing. I can find no evidence of it in MariaDB's logs, or Lucee's logs.
To simplify this, I have placed a simplified version of the query directly where the function call goes.
The simplified query is as follows
QueryExecute(sql = "INSERT INTO MyMessages (AuthorID, mSubject, mDate, mContents)
Values (21, 'direct', Now(), '{}')",
options = {datasource = "dsn_global"})
I know for a fact that the logical flow is reaching this query, even though it isn't firing, because if I remove the datasource specification, I get an error that my application's default datasource doesn't contain a table MyMessages (which it shouldn't). If I set the datasouce again, all evidence of the query disappears.
I query this datasource in other parts of my application, and it works fine including working with this table.
I am aware that this issue probably sounds like something I'm misunderstanding, but QueryExecute is being called, it just isn't doing anything. It moves on to the code after it.