Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 10 of 10 total |
SQL Parameter not working |
Fri, Oct 8 2021 10:31 AM | Permanent Link |
Greg Hallam Microcalm Solutions Inc | When I run the following SQL it works fine:
SELECT E.ID, E.Name, E.Position FROM employee E WHERE NOT E.ID IN (SELECT employeeID FROM sessiondetails WHERE sessionID IN (SELECT ID FROM session WHERE topicID= :topicID)) ORDER BY E.Position, E.name When I change the parameter and reopen the query it returns the first result. Unprepare doesn't seem to help. I have had to resort to replacing the parameter string in the query and that work fine. Is there an error in my logic or expectations? |
Fri, Oct 8 2021 1:45 PM | Permanent Link |
Fernando Dias Team Elevate | Greg,
Try: SELECT E.ID, E.Name, E.Position FROM employee E WHERE E.ID NOT IN (SELECT employeeID FROM sessiondetails WHERE sessionID IN (SELECT ID FROM session WHERE topicID= :topicID)) ORDER BY E.Position, E.name -- Fernando Dias [Team Elevate] |
Sat, Oct 9 2021 3:02 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Greg
Without your tables I can't try and reproduce. What it sounds like is that the parameter is not being replaced. Can you try running in EDBManager where you can see the parameters. If it works there its something you're doing and "all" we have to do is figure out what, if it doesn't it needs reporting to Tim as a bug. Roy Lambert |
Sat, Oct 9 2021 1:51 PM | Permanent Link |
Greg Hallam Microcalm Solutions Inc | Fernando, that was the original syntax that I had used so it is very well tested with the same results.
Roy, the error does exist in DBManager. the first query works fine but any subsequent query after a parameter change will provide the results of the first query again. The unprepare button does correct the situation and provide the correct results. I will have to check the use of prepare/unprepare in DBManager to the tests that I had done on the same subject as we got different results. Regardless having to unprepare kind of defeats the purpose of using parameters doesn't it? |
Sat, Oct 9 2021 9:31 PM | Permanent Link |
Terry Swiers | Hi Greg,
There was an issue back in 2.31 that behaved like this. ( https://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=2.35&incident=4767 ). Any chance you are running 2.31? |
Sun, Oct 10 2021 9:07 PM | Permanent Link |
Greg Hallam Microcalm Solutions Inc | Terry Swiers wrote:
Hi Greg, There was an issue back in 2.31 that behaved like this. ( https://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=2.35&incident=4767 ). Any chance you are running 2.31? Server is 2.34 Build 1 Client is 2.31 Build 10 I will upgrade and recheck. That's embarrassing . . . |
Sun, Oct 10 2021 9:31 PM | Permanent Link |
Greg Hallam Microcalm Solutions Inc | Version 236 Build 1 still has the issue in DB Manager
|
Tue, Oct 12 2021 4:14 PM | Permanent Link |
Terry Swiers | Hi Greg,
I can reproduce this. Have you reported this? If not, I can get a reproducible test case set up and get it sent in. |
Wed, Oct 13 2021 12:27 PM | Permanent Link |
Terry Swiers | Hi Greg,
I went ahead and report this as I was able to get a test case created rather easily. |
Wed, Oct 13 2021 9:40 PM | Permanent Link |
Greg Hallam Microcalm Solutions Inc | Thanks Terry, it would have been difficult for me to separate the tables I was using into a test case.
|
This web page was last updated on Tuesday, April 23, 2024 at 08:10 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |