Use the recommended FETCH NEXT x ROWS clause instead of LIMIT x

[phansys]

LIMIT x and OFFSET y are considered alternative syntax.

See:

• https://www.ibm.com/docs/en/i/7.3?topic=reference-whats-new-i-73;
• https://www.ibm.com/docs/en/i/7.3?topic=cursor-example-using-offset-clause;
• https://www.ibm.com/docs/en/i/7.3?topic=subselect-fetch-clause;

[alanseiden]

Not sure about that. The IBM example was for a stored procedure using a cursor. Is that how Doctrine works?

[codecov]

Codecov Report

Merging #63 (46735fe) into master (78b7abf) will decrease coverage by 0.89%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #63      +/-   ##
============================================
- Coverage     36.69%   35.81%   -0.89%     
- Complexity       88       89       +1     
============================================
  Files             8        8              
  Lines           218      215       -3     
============================================
- Hits             80       77       -3     
  Misses          138      138              

Impacted Files	Coverage Δ
src/Platform/DB2IBMiPlatform.php	45.45% <100.00%> (-4.55%)	⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[phansys]

Not sure about that. The IBM example was for a stored procedure using a cursor. Is that how Doctrine works?

Both variants are working, but I'm proposing this change because now I'm aware about this note:

The keywords FIRST and NEXT can be used interchangeably. The result is unchanged; however, using the keyword NEXT is more readable when the offset-clause is used.
The following are supported for compatibility with SQL used by other database products. These alternatives are non-standard and should not be used.

[alanseiden]

@phansys Seems okay to me.