Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
I33Buckler commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1751540744 > @I33Buckler If you are able to restart it, from where it left off, does it error at the same location? Or, the same distance from where it started? At the same location.

Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
jrgemignani commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1751539664 @I33Buckler If you are able to restart it, from where it left off, does it error at the same location? Or, the same distance from where it started? -- This is an automated message

Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
I33Buckler commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1751536916 > @I33Buckler Is the rte not found always the same or different? The RTE value depends on the content of service_key in the effected row -- This is an automated message from

Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
jrgemignani commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1751536419 @I33Buckler Is the rte not found always the same or different? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

Re: [PR] In-line code formatting for the Introduction section [age-website]

2023-10-06 Thread via GitHub
Allison-E commented on PR #211: URL: https://github.com/apache/age-website/pull/211#issuecomment-1751460996 I had issues while rebasing, and this PR got closed in the process. The new PR is #218. -- This is an automated message from the Apache Git Service. To respond to the message,

[PR] In-line code formatting for the Introduction section [age-website]

2023-10-06 Thread via GitHub
Allison-E opened a new pull request, #218: URL: https://github.com/apache/age-website/pull/218 It's easier to identify the SQL clause WHERE when written as an in-line code, `WHERE`. This PR updates all SQL commands, Cypher commands, AGE and PostgreSQL data types in the Introduction

Re: [PR] In-line code formatting for AGE clauses in the Functions Section [age-website]

2023-10-06 Thread via GitHub
Allison-E commented on PR #213: URL: https://github.com/apache/age-website/pull/213#issuecomment-1751459554 I had issues rebasing, and this PR got closed in the process. The new PR is #217. -- This is an automated message from the Apache Git Service. To respond to the message, please log

[PR] In-line code formatting for AGE clauses in the Functions Section [age-website]

2023-10-06 Thread via GitHub
Allison-E opened a new pull request, #217: URL: https://github.com/apache/age-website/pull/217 It's easier to identify the Cypher function sum() when formatted as an in-line code, `sum()`. This PR formats all AGE code in the Functions section of the documentation to in-line codes.

Re: [PR] In-line code formatting for the Introduction section [age-website]

2023-10-06 Thread via GitHub
Allison-E closed pull request #211: In-line code formatting for the Introduction section URL: https://github.com/apache/age-website/pull/211 -- 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

Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
I33Buckler commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1751373836 > @I33Buckler Is it always failing on the same row? What happens if you remove that row? Fails in exactly the same row number regardless of content. -- This is an

Re: [PR] In-line code formatting for AGE clauses in the Functions Section [age-website]

2023-10-06 Thread via GitHub
Allison-E closed pull request #213: In-line code formatting for AGE clauses in the Functions Section URL: https://github.com/apache/age-website/pull/213 -- 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

Re: [I] drop_graph('graph_name') fails to Delete Graph [age]

2023-10-06 Thread via GitHub
markgomer closed issue #1178: drop_graph('graph_name') fails to Delete Graph URL: https://github.com/apache/age/issues/1178 -- 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

Re: [DISCUSS] Apache AGE 1.4.0 Release for PostgreSQL 12

2023-10-06 Thread Rafsun Masud
Checked: - Signature and hash - LICENSE and notice - Links and Tags - Unexpected binary files (none) Regards, Rafsun Masud On Fri, Oct 6, 2023 at 10:28 AM John Gemignani wrote: > Dear Apache Community, > > We would like to open a discussion for the Apache AGE release 1.4.0 for > PostgreSQL 12.

[DISCUSS] Apache AGE 1.4.0 Release for PostgreSQL 12

2023-10-06 Thread John Gemignani
Dear Apache Community, We would like to open a discussion for the Apache AGE release 1.4.0 for PostgreSQL 12. To learn more about Apache AGE, please see http://age.apache.org/ Functionalities included and addressed in this release are:

Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
jrgemignani commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1751037956 @I33Buckler Is it always failing on the same row? What happens if you remove that row? -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] Unexpected termination on looping cypher query - could not find rte [age]

2023-10-06 Thread via GitHub
I33Buckler commented on issue #1260: URL: https://github.com/apache/age/issues/1260#issuecomment-1750150494 > @I33Buckler Have you tried against the **master** branch which is also at PostgreSQL version 15? Yes. I have version 1.4.0 installed from the master branch.