dev  

Messages by Thread

• [DISCUSS] Apache AGE 1.6.0 Release for PostgreSQL 15 John Gemignani
• [I] The image contains 4 high vulnerabilitiesDocker DX (docker-language-server)(critical_high_vulnerabilities) [age] via GitHub
• [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
  • Re: [I] Creating more than 41 vlabels causes drop_grapth to fail with "label (relation) cache corrupted" [age] via GitHub
• [I] Regression in string concatenation using the + operator [age] via GitHub
  • Re: [I] Regression in string concatenation using the + operator [age] via GitHub
  • Re: [I] Regression in string concatenation using the + operator [age] via GitHub
  • Re: [I] Regression in string concatenation using the + operator [age] via GitHub
  • Re: [I] Regression in string concatenation using the + operator [age] via GitHub
  • Re: [I] Regression in string concatenation using the + operator [age] via GitHub
  • Re: [I] Regression in string concatenation using the + operator [age] via GitHub
• [I] Regarding Vulnerability GO-2024-2587 and Its Impact on Current apacheAGE Go Driver [age] via GitHub
  • Re: [I] Regarding Vulnerability GO-2024-2587 and Its Impact on Current apacheAGE Go Driver [age] via GitHub
  • Re: [I] Regarding Vulnerability GO-2024-2587 and Its Impact on Current apacheAGE Go Driver [age] via GitHub
• [I] Unresponsive frontent with `Line 23:22: Unable to resolve path to module 'cytoscape/src/util' [age-viewer] via GitHub
• Re: [D] Does Apache AGE support storing vector embeddings and similarity search? [age] via GitHub
• [I] Importing Graph from Files - with using docker and python driver - not able to import data without any error shown [age] via GitHub
• [I] IS there any performance benchmark between `age` and Graph-native Database like `neo4j` ? [age] via GitHub
  • Re: [I] IS there any performance benchmark between `age` and Graph-native Database like `neo4j` ? [age] via GitHub
• [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
  • Re: [I] Object string to agtype conversion difference between 1.5.0 and 1.6.0 [age] via GitHub
• [I] Support psycopg2-binary or psycopg (3) [age] via GitHub
• [D] Supported cloud providers of Apache AGE [age] via GitHub
  • Re: [D] Supported cloud providers of Apache AGE [age] via GitHub
• [RESULT][VOTE] Apache AGE 1.6.0 Release for PostgreSQL 17 John Gemignani
• [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
  • Re: [D] Simplify this query and remove redundancy [age] via GitHub
• [I] Passing agtype argument to prepared statement in Golang [age] via GitHub
• [I] Support: PostgreSQL 18 [age] via GitHub
  • Re: [I] Support: PostgreSQL 18 [age] via GitHub
  • Re: [I] Support: PostgreSQL 18 [age] via GitHub
  • Re: [I] Support: PostgreSQL 18 [age] via GitHub
  • Re: [I] Support: PostgreSQL 18 [age] via GitHub
• [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 17 John Gemignani
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 17 Taha Naveed
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 17 Muhammad Shoaib
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 17 Eya Badal
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 17 John Gemignani
• [I] Add AGE java driver to Maven Central [age] via GitHub
• [D] Master branch with PostgreSQL 18 [age] via GitHub
• Re: [D] What's the Status of Apache AGE? [age] via GitHub
  • Re: [D] What's the Status of Apache AGE? [age] via GitHub
  • Re: [D] What's the Status of Apache AGE? [age] via GitHub
  • Re: [D] What's the Status of Apache AGE? [age] via GitHub
• [D] Apache AGE Status Updates [age] via GitHub
  • Re: [D] Apache AGE Status Updates [age] via GitHub
• [DISCUSS] Apache AGE 1.6.0 Release for PostgreSQL 17 John Gemignani
  • Re: [DISCUSS] Apache AGE 1.6.0 Release for PostgreSQL 17 John Gemignani
• [I] Error passing strings containing apostrophes as parameters [age] via GitHub
  • Re: [I] Error passing strings containing apostrophes as parameters [age] via GitHub
  • Re: [I] Error passing strings containing apostrophes as parameters [age] via GitHub
• [RESULT][VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 John Gemignani
• [I] How can i create a vertex having more than 50 properties. [age] via GitHub
  • Re: [I] How can i create a vertex having more than 50 properties. [age] via GitHub
  • Re: [I] How can i create a vertex having more than 50 properties. [age] via GitHub
  • Re: [I] How can i create a vertex having more than 50 properties. [age] via GitHub
• [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 John Gemignani
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 Muhammad Taha
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 Muhammad Taha
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 Muhammad Shoaib
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 Muhammad Shoaib
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 Eya Badal
  • Re: [VOTE] Apache AGE 1.6.0 Release for PostgreSQL 16 John Gemignani
• Re: [I] Docs for UNWIND clause are not available [age-website] via GitHub
• Re: [PR] Fix join example in advanced.md [age-website] via GitHub
  • Re: [PR] Fix join example in advanced.md [age-website] via GitHub
• [PR] Update prepared_statements.md [age-website] via GitHub
  • [GitHub] [age-website] dehowef closed pull request #105: Update prepared_statements.md via GitHub
  • Re: [PR] Update prepared_statements.md [age-website] via GitHub
  • Re: [PR] Update prepared_statements.md [age-website] via GitHub
• [PR] Update actions in build-documentation.yml [age-website] via GitHub
  • Re: [PR] Update actions in build-documentation.yml [age-website] via GitHub
• [DISCUSS] Apache AGE 1.6.0 Release for PostgreSQL 16 John Gemignani
  • Re: [DISCUSS] Apache AGE 1.6.0 Release for PostgreSQL 16 Muhammad Taha
  • Re: [DISCUSS] Apache AGE 1.6.0 Release for PostgreSQL 16 John Gemignani
• [D] Release v1.6.0 for PG16 [age] via GitHub
• [PR] Make clean usage for Prepared Statements (clone pr#105) [age-website] via GitHub
  • Re: [PR] Make clean usage for Prepared Statements (clone pr#105) [age-website] via GitHub
  • Re: [PR] Make clean usage for Prepared Statements (clone pr#105) [age-website] via GitHub
• [I] docker image latest tag does not contain arm64 build [age] via GitHub
  • Re: [I] docker image latest tag does not contain arm64 build [age] via GitHub
  • Re: [I] docker image latest tag does not contain arm64 build [age] via GitHub
  • Re: [I] docker image latest tag does not contain arm64 build [age] via GitHub
• [I] left() function fails to handle large negative integers correctly [age] via GitHub
  • Re: [I] left() function fails to handle large negative integers correctly [age] via GitHub
  • Re: [I] left() function fails to handle large negative integers correctly [age] via GitHub
• [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
  • Re: [I] Unexpected behavior when using empty string '' in string functions in Apache AGE [age] via GitHub
• [I] how to not generate subplan instead anti join [age] via GitHub
• [I] Default database connection [age-viewer] via GitHub
• [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
  • Re: [I] Performance Issue in Edge Creation for Large Tables and Index Creation [age] via GitHub
• [I] AGE extension requires explicit commit after LOAD/SET for proper initialization in non-autocommit clients [age] via GitHub
• [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
  • Re: [I] Major Performance Difference: SQL vs. Cypher for Aggregation/Ordering [age] via GitHub
• [I] error while running Age-Viewer using : npm run start [age-viewer] via GitHub
  • Re: [I] error while running Age-Viewer using : npm run start [age-viewer] via GitHub
  • Re: [I] error while running Age-Viewer using : npm run start [age-viewer] via GitHub
  • Re: [I] error while running Age-Viewer using : npm run start [age-viewer] via GitHub
  • Re: [I] error while running Age-Viewer using : npm run start [age-viewer] via GitHub
  • Re: [I] error while running Age-Viewer using : npm run start [age-viewer] via GitHub
• [I] create … with … The execution plan of match is abnormal [age] via GitHub
  • Re: [I] create … with … The execution plan of match is abnormal [age] via GitHub
  • Re: [I] create … with … The execution plan of match is abnormal [age] via GitHub
  • Re: [I] create … with … The execution plan of match is abnormal [age] via GitHub
• [I] Schema name should be configurable [age] via GitHub
• [I] Performance issue [age] via GitHub
  • Re: [I] Performance issue [age] via GitHub
  • Re: [I] Performance issue [age] via GitHub
• Re: [I] List comprehensions [age] via GitHub
• [PR] add missing column name to example query in advanced.md [age-website] via GitHub
  • Re: [PR] add missing column name to example query in advanced.md [age-website] via GitHub

• Earlier messages