You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think limit 0 is meaningless. If you want to limit 0, why not just return [] without selecting database.
I'm not to talk about whether it's meaningful to limit 0, but the correctness of the result. Since the result is not the same as what it is expected to return when using SQL, then that's the problem, isn't it?
OTOH, the following is quoted from MySQL docs regarding the usage of limit 0
LIMIT 0 quickly returns an empty set. This can be useful for checking the validity of a query. It can also be employed to obtain the types of the result columns within applications that use a MySQL API that makes result set metadata available.
The following lines
bun/query_select.go
Lines 634 to 637 in 7cd855e
causes bun omits to append
Limit 0
when selecting rows, resulting in returning all of the rows, which is not consistent with the expected empty setThe text was updated successfully, but these errors were encountered: