MironAtHome commented on issue #1629: URL: https://github.com/apache/age/issues/1629#issuecomment-1977018339
I think it is not really question of match, but a question of what "optional" means. Based on what I have gathered from the documentation ( provided in the comments ) optional indicates outer kind of relationship. Which means that in case of an empty set(s) on one of the sides, it is treated as an null, whilst the other one, depending on the operator, suppose to either furnish an matching row, or no row. So, if one is to read it with an eye to standard sql, this falls into the case of full outer join. It would be very nice if there is a chance to clarify similar against some alternate engine? I didn't treat it with high severity, since performing hierarchical match, where 1st level is required and 2nd level is optional, query works correctly. So, we can do left outer join right now, and that gives us a chance with, perhaps one additional query step, satisfy need to perform outer join. However, if query could pick up proper outer join behavior, it would be helpful, particularly for some of the corner cases used to test data quality. Hope this clarification helps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
