Re: SQL/JSON: FOR ORDINALITY bug

2022-05-09 Thread Andrew Dunstan
On 2022-05-04 We 16:09, Erik Rijkers wrote: > Op 04-05-2022 om 21:12 schreef Andrew Dunstan: >> > > I don't see how rowseq can be anything but 1.  Each invocation of >>> >>> >>> After some further experimentation, I now think you must be right, >>> David. >>> >>> Also, looking at the DB2

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-04 Thread David G. Johnston
On Wed, May 4, 2022 at 1:43 PM David G. Johnston wrote: > On Wed, May 4, 2022 at 1:09 PM Erik Rijkers wrote: > >> Op 04-05-2022 om 21:12 schreef Andrew Dunstan: >> > >> >> I don't see how rowseq can be anything but 1. Each invocation of >> >> >> >> >> >> After some further experimenta

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-04 Thread David G. Johnston
On Wed, May 4, 2022 at 1:09 PM Erik Rijkers wrote: > Op 04-05-2022 om 21:12 schreef Andrew Dunstan: > > > > I don't see how rowseq can be anything but 1. Each invocation of > >> > >> > >> After some further experimentation, I now think you must be right, > David. > >> > >> Also, lookin

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-04 Thread Erik Rijkers
Op 04-05-2022 om 21:12 schreef Andrew Dunstan: I don't see how rowseq can be anything but 1.  Each invocation of After some further experimentation, I now think you must be right, David. Also, looking at the DB2 docs:   https://www.ibm.com/docs/en/i/7.2?topic=data-using-json-table     (s

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-04 Thread Andrew Dunstan
On 2022-05-04 We 10:39, Erik Rijkers wrote: > Op 04-05-2022 om 13:55 schreef Andrew Dunstan: >> >> On 2022-05-03 Tu 20:39, David G. Johnston wrote: >>> On Tue, May 3, 2022 at 5:27 PM Andrew Dunstan >>> wrote: >>> >>> >>> On 2022-05-03 Tu 11:19, Erik Rijkers wrote: >>> > Hi >>> > >

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-04 Thread Erik Rijkers
Op 04-05-2022 om 13:55 schreef Andrew Dunstan: On 2022-05-03 Tu 20:39, David G. Johnston wrote: On Tue, May 3, 2022 at 5:27 PM Andrew Dunstan wrote: On 2022-05-03 Tu 11:19, Erik Rijkers wrote: > Hi > > I've copied some statements from the .pdf called: > "TECHNICAL RE

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-04 Thread Andrew Dunstan
On 2022-05-03 Tu 20:39, David G. Johnston wrote: > On Tue, May 3, 2022 at 5:27 PM Andrew Dunstan wrote: > > > On 2022-05-03 Tu 11:19, Erik Rijkers wrote: > > Hi > > > > I've copied some statements from the .pdf called: > > "TECHNICAL REPORT ISO/IEC TR 19075-6   First edition

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-03 Thread David G. Johnston
On Tue, May 3, 2022 at 5:27 PM Andrew Dunstan wrote: > > On 2022-05-03 Tu 11:19, Erik Rijkers wrote: > > Hi > > > > I've copied some statements from the .pdf called: > > "TECHNICAL REPORT ISO/IEC TR 19075-6 First edition 2017-03 > > Part SQL Notation support 6: (JSON) for JavaScript Object" > >

Re: SQL/JSON: FOR ORDINALITY bug

2022-05-03 Thread Andrew Dunstan
On 2022-05-03 Tu 11:19, Erik Rijkers wrote: > Hi > > I've copied some statements from the .pdf called: > "TECHNICAL REPORT ISO/IEC TR 19075-6   First edition 2017-03 > Part SQL Notation support 6: (JSON) for JavaScript Object" > (not available anymore although there should be a similar replacemen

SQL/JSON: FOR ORDINALITY bug

2022-05-03 Thread Erik Rijkers
Hi I've copied some statements from the .pdf called: "TECHNICAL REPORT ISO/IEC TR 19075-6 First edition 2017-03 Part SQL Notation support 6: (JSON) for JavaScript Object" (not available anymore although there should be a similar replacement file) In that pdf I found the data and statement (cal