friday-james commented on issue #170:
URL: https://github.com/apache/age-viewer/issues/170#issuecomment-2817614670
why is it not merged yet? postgre 16 is quite common
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
tumluliu commented on issue #170:
URL: https://github.com/apache/age-viewer/issues/170#issuecomment-2442011501
@jrgemignani thank you for pointing me to that comment. What a sad news for
such an amazing project ): I anyway had applied the #171 patch locally and it
fixed the metadata problem
jrgemignani commented on issue #170:
URL: https://github.com/apache/age-viewer/issues/170#issuecomment-2441976823
@tumluliu Please see this comment as it may likely apply here as well:
https://github.com/apache/age/issues/2111#issuecomment-2441903180
--
This is an automated message from t
tumluliu commented on issue #170:
URL: https://github.com/apache/age-viewer/issues/170#issuecomment-2441928686
Any plan to merge the PR #171 ?
--
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
markgomer commented on issue #170:
URL: https://github.com/apache/age-viewer/issues/170#issuecomment-2096697286
Pull request #171 should fix this. @eyab @aked21
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
adrioui opened a new issue, #170:
URL: https://github.com/apache/age-viewer/issues/170
Error on the backend when loading a metadata's version that does not
compatible with the viewer.
I am using this image: apache/age:latest.
The error code is 500 in the backend. It says "SQL does no
