Hi all,
the issue was not with the database nor with the jdbc driver but with the
implementation of call itself :
The implementation of execute does not close the connection
@Override
public boolean execute() {
try {
...
} catch (LockTimeoutException exception) {
throw exception;
} catch
There is no natural order for rows in SQL. If you care about the order
of the rows in your result, you must always specify an ORDER BY
clause.
Instead of putting the ORDER BY in the definition of the view, put the
ORDER BY on the SELECT statement from the view.
That is, don't do:
Sorting behavior is only defined for the columns in the ORDER BY clause.
If a column is not included in the ORDER BY clause, then its sort order
can be arbitrary and not even consistent across executions of the query.
Hope this helps,
-Rick
On 4/27/22 4:35 AM, John English wrote:
I have a
I have a Java method which displays a view as an HTML table. The method
has parameters to specify the sort column (default is the first column
ascending), filters to select specific rows, and so on.
Recently I came across an oddity which I can't figure out. Consider the
following table and
On 27/04/2022 17:37, Bryan Pendleton wrote:
> There is no natural order for rows in SQL. If you care about the order
> of the rows in your result, you must always specify an ORDER BY
> clause.
Well, the "default" ordering (no ORDER BY clause) reflects the order of
insertion. It seems odd to me
