On Wed, Sep 9, 2020 at 10:05 AM Lukas Eder <[email protected]> wrote:
> On Tue, Sep 8, 2020 at 6:15 PM Aner Perez <[email protected]> wrote: > >> So what you're saying is that my change "fixed" the query but only by >> coincidence. The only part I don't understand is how the 2nd result set I >> provided in my initial post above is possible. The data I provided is >> complete with some simple hand editing that I triple checked (but not >> quadruple checked). How is it possible that in some result rows the >> *worker* column has an array of values in it but the *level1* column >> which should be the first element of that array is null? Notice that both >> result sets have the same number of columns and the same the same numeric >> data albeit in a different order. It's just the level1, level2 and level3 >> columns that seem to have null in them for all groupings except for the >> first. >> > > I can have a look if I know how to reproduce this. An MCVE would be > helpful, we have a template here: https://github.com/jOOQ/jOOQ-mcve > I was mostly focusing on the ORDER BY issue, which should be easiest to > fix. Quite possibly, something else is tampering with the results here, > which I'm overlooking > OK, you figured it out in the next email already, great to hear! It does seem to be a bug in PostgreSQL when you show it like this. Thanks for following up! > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO49eP%3DwkrWxy%3DS1BhC%3DpvnvPRuxgDj3%3D%3DsTrOrYYg%2BB0A%40mail.gmail.com.
