Bug #3020 | subselect still not work in FROM clause in prepared statements | ||
---|---|---|---|
Submitted: | 1 Mar 2004 2:47 | Modified: | 18 Apr 2004 9:21 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.2 | OS: | Linux (Linux) |
Assigned to: | Oleksandr Byelkin | CPU Architecture: | Any |
[1 Mar 2004 2:47]
[ name withheld ]
[1 Mar 2004 3:06]
[ name withheld ]
Stack trace file
Attachment: stack.trc (application/octet-stream, text), 3.45 KiB.
[1 Mar 2004 20:19]
Wil Williams
Also experienced using 4.1.1alpha. It seems to be a server bug since it causes the server to terminate all (other?) connections and produce this message (when running the server manually from the command line as a normal user): Number of processes running now: 0 040302 12:11:23 mysqld restarted
[1 Mar 2004 20:24]
Wil Williams
I am using JDBC connector "mysql-connector-java-3.1.1-alpha-bin.jar", Debian Linux with "mysql-standard-4.1.1-alpha-pc-linux-i686". I am however doing a join rather than a subselect. The query is of form: "select fields from a,b where a.f=b.f and id=? order by something". I get around the problem by using statements. It's also 100% reliable/repeatable so it's not a major issue since it's easily found an removed.
[6 Mar 2004 13:38]
Dean Ellis
Verified against 4.1.2, and changing the category as this is an error in the server rather than Connector/J. Thank you.
[8 Apr 2004 13:40]
Oleksandr Byelkin
ChangeSet 1.1783 04/04/08 23:28:47 bell@sanja.is.com.ua +2 -0 fixed subquery in the FROM clause with parameter (BUG#3020)
[18 Apr 2004 9:21]
Oleksandr Byelkin
Thank you for bugreport. Fix for this bug is pushed to our internal source repository and vill be present in next server release