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
Currently in some test, for example for get_acoustic_detections(), limit=TRUE is used to save on time, however, it's not guaranteed that the output of the query will be the same every time if we don't add an ORDER BY to the query
Currently in some test, for example for
get_acoustic_detections()
, limit=TRUE is used to save on time, however, it's not guaranteed that the output of the query will be the same every time if we don't add an ORDER BY to the queryhttps://stackoverflow.com/questions/37470753/if-i-run-a-sql-statement-multiple-times-with-row-limit-will-i-get-the-same-resu
If using a limit, we should probably add ORDER BY on the primary key to the query to preserve repeatability for testing
https://stackoverflow.com/questions/39680598/querying-with-limit-and-offset-is-there-a-chance-to-have-different-results-with
https://stackoverflow.com/questions/59496627/why-does-sql-limit-clause-returns-random-rows-for-every-query
The text was updated successfully, but these errors were encountered: