Bug #24489 @@sql_select_limit applies to stored functions, triggers, events
| Submitted: | 21 Nov 2006 22:16 | Modified: | 5 Dec 2006 16:58 |
|---|---|---|---|
| Reporter: | Konstantin Osipov (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
| Version: | 5.0 BK, 5.1 BK | OS: | Linux (Linux) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | sql_select_limit, stored procedure, trigger | ||
[21 Nov 2006 22:16]
Konstantin Osipov
[21 Nov 2006 22:28]
Konstantin Osipov
When fixing this bug, we should not only look at @@sql_select_limit, but at all variables that affect behaviour of queries: - may cause a runtime execution error - may effect in a different result set returned by a query. We can employ one of the following strategies: - reset all these variables to their default values when starting execution of a stored program. In this case, what happens if a default value changes from version to version of the server? - store the variables along with the definition of the stored program and activate when the stored program is being executed.
[22 Nov 2006 9:56]
Sveta Smirnova
Thank you for the report. Verified as described on Linux using last BK sources.
[20 Feb 2008 19:39]
Omer Barnir
workaround: use explicit LIMIT clause in SELECT
[21 Mar 2013 1:24]
Paul DuBois
Per Bug#65657, the statement about sql_select_limit not applying within stored programs has been removed from the manual.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.