[GitHub] [incubator-age] jrgemignani commented on issue #220: VLE still has a bug when I try to run PL/pgSQL functions with VLE statements inside

[GitBox <gi...@apache.org>]

jrgemignani commented on issue #220:
URL: https://github.com/apache/incubator-age/issues/220#issuecomment-1136065577

   I have reproduced and found what the issue is with this particular bug. It is not related to the other VLE bug, other than also being an issue with transaction ids. So, if you are happy with that issue being resolved, please close that ticket.
   
   The issue here has to do with the way the VLE caches contexts, which are expensive to recreate. The VLE stores the grammar node IDs as an index into a cache for later retrieval for chained **non-updating commands** with a VLE component.
   
   Grammar node IDs change from position to position, line to line. In other words, they are unique to that particular VLE command. The problem here is that the grammar node does not change as it is **in a procedure**. So, the VLE caching mechanism sees it as repeating a previous command.
   
   When writing the caching mechanism, I must have overlooked the possibility of the a VLE component inside a procedure where the grammar node ID would be static. I need to think about how this can be resolved and what the implications would be.


-- 
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-unsubscribe@age.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org