Re: [I] The Go driver becomes "undefined: parser", and the application cannot be built. [age]

2024-01-17 Thread via GitHub
jrgemignani commented on issue #1455: URL: https://github.com/apache/age/issues/1455#issuecomment-1897584117 Both the README and install.sh files aren't very good. If you look at the install file, you will basically need to - 1. Make sure that you have installed and selected the

Re: [I] The Go driver becomes "undefined: parser", and the application cannot be built. [age]

2024-01-17 Thread via GitHub
jrgemignani commented on issue #1455: URL: https://github.com/apache/age/issues/1455#issuecomment-1897560429 @maehara-n You need to build those files by executing generate.sh - ``` [jgemignani@cent7nuc7i5bnk age]$ ll ../parser/ total 100 -rw-rw-r--. 1 jgemignani jgemignani

[VOTE] Apache AGE 1.5.0 Release for PostgreSQL 16

2024-01-17 Thread John Gemignani
Dear Apache Community, Please carefully read all instructions as they may have changed since the last vote thread. This is an official vote for Apache AGE release 1.5.0 for PostgreSQL 16. To learn more about Apache AGE, please see http://age.apache.org/ Functionalities included and addressed

Re: [DISCUSS] Apache AGE 1.5.0 Release for PostgreSQL 16

2024-01-17 Thread John Gemignani
Dear Apache Community, Since there are no objections, I am closing the [DISCUSS] thread and will open the official [VOTE] thread for Apache AGE 1.5.0 for PostgreSQL 16 shortly. Thank you for your time, John Gemignani On Wed, Jan 10, 2024 at 8:56 AM Dehowe Feng wrote: > Updating to Postgres

Re: [I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub
rafsun42 commented on issue #1513: URL: https://github.com/apache/age/issues/1513#issuecomment-1896431742 This can be a project. The other executors may have similar issues. #1446 is a related one. -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] No update path to 1.5.0 [age]

2024-01-17 Thread via GitHub
jrgemignani commented on issue #1508: URL: https://github.com/apache/age/issues/1508#issuecomment-1896336367 @guruguruguru Not a problem, it happens. There is no way, **currently**, to upgrade from one version of AGE in say, PostgreSQL version 12 to the same version of AGE in

Re: [I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub
jrgemignani commented on issue #1513: URL: https://github.com/apache/age/issues/1513#issuecomment-1896292602 @Zainab-Saad If you are planning on creating a PR to fix this, please note it here :) -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub
jrgemignani commented on issue #1513: URL: https://github.com/apache/age/issues/1513#issuecomment-1896291094 @Zainab-Saad Good catch! -- 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

Re: [I] Error when trying to run with "npm run start" [age-viewer]

2024-01-17 Thread via GitHub
tsmanuelanton commented on issue #166: URL: https://github.com/apache/age-viewer/issues/166#issuecomment-1896181898 you can fix this executing before `export NODE_OPTIONS=--openssl-legacy-provider` -- This is an automated message from the Apache Git Service. To respond to the message,

[I] Invalid reuse of previous clause variable in succeeding CREATE clause [age]

2024-01-17 Thread via GitHub
Zainab-Saad opened a new issue, #1513: URL: https://github.com/apache/age/issues/1513 **Describe the bug** The succeeding CREATE clause is letting the reuse of variable of the previous CREATE. **How are you accessing AGE (Command line, driver, etc.)?** psql **What is the

Re: [I] Happy new years [age-website]

2024-01-17 Thread via GitHub
itsdheerajdp commented on issue #245: URL: https://github.com/apache/age-website/issues/245#issuecomment-1895518044 Can you please clearly explain me what you want me to do as i am confused because PR is already merged so what to do now?? -- This is an automated message from the Apache