dev  

Messages by Thread

• [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
• [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
• [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
• [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
  • Re: [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
• Re: [I] Index advice for hop queries [age] via GitHub
• Re: [D] New Tag Post-1.5.0 to Include Recent Commits [age] via GitHub
  • Re: [D] New Tag Post-1.5.0 to Include Recent Commits [age] via GitHub
  • Re: [D] New Tag Post-1.5.0 to Include Recent Commits [age] via GitHub
  • Re: [D] New Tag Post-1.5.0 to Include Recent Commits [age] via GitHub
  • Re: [D] New Tag Post-1.5.0 to Include Recent Commits [age] via GitHub
• [I] CREATE EXTENSION pg_stat_statements fails when AGE 1.5.0 is in shared_preload_libraries [age] via GitHub
  • Re: [I] CREATE EXTENSION pg_stat_statements fails when AGE 1.5.0 is in shared_preload_libraries [age] via GitHub
• [I] Error is reported when concurrently merging nodes/edges [age] via GitHub
  • Re: [I] Error is reported when concurrently merging nodes/edges [age] via GitHub
  • Re: [I] Error is reported when concurrently merging nodes/edges [age] via GitHub
  • Re: [I] Error is reported when concurrently merging nodes/edges [age] via GitHub
• [I] Performance issue when upserting 10k+ edges using MERGE [age] via GitHub
  • Re: [I] Performance issue when upserting 10k+ edges using MERGE [age] via GitHub
  • Re: [I] Performance issue when upserting 10k+ edges using MERGE [age] via GitHub
  • Re: [I] Performance issue when upserting 10k+ edges using MERGE [age] via GitHub
  • Re: [I] Performance issue when upserting 10k+ edges using MERGE [age] via GitHub
  • Re: [I] Performance issue when upserting 10k+ edges using MERGE [age] via GitHub
• [I] Btree indexing in age [age] via GitHub
  • Re: [I] Btree indexing in age [age] via GitHub
• [I] Bug: load_edges_from_file Fails to Properly Import Single Property from CSV [age] via GitHub
  • Re: [I] Bug: load_edges_from_file Fails to Properly Import Single Property from CSV [age] via GitHub
• Re: [I] Bug: Unexpected Property When Loading Edges from CSV [age] via GitHub
• Regarding PR Approval Process Muhammad Taha
  • Re: Regarding PR Approval Process John Gemignani
  • Re: Regarding PR Approval Process Rafsun Masud
• [I] how to optimise this sql, its execution is extremely slow. [age] via GitHub
  • Re: [I] how to optimise this sql, its execution is extremely slow. [age] via GitHub
  • Re: [I] how to optimise this sql, its execution is extremely slow. [age] via GitHub
• [I] I have to add a line to Dockerfile make it work: RUN npm add @babel/runtime [age-viewer] via GitHub
  • Re: [I] I have to add a line to Dockerfile make it work: RUN npm add @babel/runtime [age-viewer] via GitHub
• Disable auto-closing issues Rafsun Masud
  • Re: Disable auto-closing issues Umar Hayat
  • Re: Disable auto-closing issues John Gemignani
  • Re: Disable auto-closing issues Muhammad Taha
  • Re: Disable auto-closing issues John Gemignani
  • Re: Disable auto-closing issues Muhammad Taha
  • Re: Disable auto-closing issues John Gemignani
• [I] Dynamically unpacking properties with UNWIND and SET s = row fails with Error: properties() argument must resolve to a scalar value [age] via GitHub
  • Re: [I] Dynamically unpacking properties with UNWIND and SET s = row fails with Error: properties() argument must resolve to a scalar value [age] via GitHub
  • Re: [I] Dynamically unpacking properties with UNWIND and SET s = row fails with Error: properties() argument must resolve to a scalar value [age] via GitHub
• [I] Frontend setup error in cytoscape [age-viewer] via GitHub
  • Re: [I] Frontend setup error in cytoscape [age-viewer] via GitHub
  • Re: [I] Frontend setup error in cytoscape [age-viewer] via GitHub
  • Re: [I] Frontend setup error in cytoscape [age-viewer] via GitHub
• [I] Using PostgreSQL version 16.6 and its corresponding age version 1.5.0, importing a database using a CSV file is not possible when there is only one attribute in the CSV file [age] via GitHub
  • Re: [I] Using PostgreSQL version 16.6 and its corresponding age version 1.5.0, importing a database using a CSV file is not possible when there is only one attribute in the CSV file [age] via GitHub
  • Re: [I] Using PostgreSQL version 16.6 and its corresponding age version 1.5.0, importing a database using a CSV file is not possible when there is only one attribute in the CSV file [age] via GitHub
• [I] From PostgreSQL 18 onwards - TupleDesc struct uses compat_attribute. TupleDescAttr() is the recommended way to access attr now, which is available on postgresql 16 [age] via GitHub
  • Re: [I] From PostgreSQL 18 onwards - TupleDesc struct uses compat_attribute. TupleDescAttr() is the recommended way to access attr now, which is available on postgresql 16 [age] via GitHub
• [I] Shortest Path Error [age] via GitHub
• [I] VLE Query on read-only replica [age] via GitHub
• [I] [maintenance] Update antlr- antlr-go lives in a new repository/module. [age] via GitHub
• [I] Bulk CSV Load doesn't work as expected [age] via GitHub
  • Re: [I] Bulk CSV Load doesn't work as expected [age] via GitHub
  • Re: [I] Bulk CSV Load doesn't work as expected [age] via GitHub
  • Re: [I] Bulk CSV Load doesn't work as expected [age] via GitHub
• [I] APOC functions supported? [age] via GitHub
• [PR] Addresses #339 and #343 [age-website] via GitHub
  • Re: [PR] Addresses #339 (UNWIND) and #343 (missing TOC links) [age-website] via GitHub
• [I] Change requirements.txt for compatible releases [age-website] via GitHub
• [I] Document indexing [age-website] via GitHub
• [I] Precedence and map functions docs [age-website] via GitHub
  • Re: [I] Precedence and map functions docs [age-website] via GitHub
• [I] Create Dockerfile for doc generation [age-website] via GitHub
• [I] AGE Installation in Ubuntu 22.04 failing [age] via GitHub
  • Re: [I] AGE Installation in Ubuntu 22.04 failing [age] via GitHub
  • Re: [I] AGE Installation in Ubuntu 22.04 failing [age] via GitHub
• [I] Indexing with where clause [age] via GitHub
  • Re: [I] Indexing with where clause [age] via GitHub
  • Re: [I] Indexing with where clause [age] via GitHub
  • Re: [I] Indexing with where clause [age] via GitHub
  • Re: [I] Indexing with where clause [age] via GitHub
• [I] Query node by graphid slow [age] via GitHub
  • Re: [I] Query node by graphid slow [age] via GitHub
  • Re: [I] Query node by graphid slow [age] via GitHub
• Re: [I] Update website to reflect only Postgres will be supported [age-website] via GitHub
  • Re: [I] Update website to reflect only Postgres will be supported [age-website] via GitHub
  • Re: [I] Update website to reflect only Postgres will be supported [age-website] via GitHub
  • Re: [I] Update website to reflect only Postgres will be supported [age-website] via GitHub
• [PR] Removed mysql, mariadb, agedb refs [age-website] via GitHub
  • Re: [PR] Removed mysql, mariadb, agedb, google tag manager refs [age-website] via GitHub
• Re: [I] Allow load_labels_from_file and load_edges_from_file to accept file data directly [age] via GitHub
• [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
  • Re: [I] load_edges_from_file parser error [age] via GitHub
• [I] Apache age viewer UI gets errored out with message can not use a pool after calling end of the pool [age-viewer] via GitHub
• [I] Properties Not Created Correctly in Cypher Query Execution [age] via GitHub
  • Re: [I] Properties Not Created Correctly in Cypher Query Execution [age] via GitHub
  • Re: [I] Properties Not Created Correctly in Cypher Query Execution [age] via GitHub
  • Re: [I] Properties Not Created Correctly in Cypher Query Execution [age] via GitHub
• Re: [I] Using geographic objects as properties with PostGIS [age] via GitHub
  • Re: [I] Using geographic objects as properties with PostGIS [age] via GitHub
• [I] Remove Google Tag Manager [age-website] via GitHub
  • Re: [I] Remove Google Tag Manager [age-website] via GitHub
  • Re: [I] Remove Google Tag Manager [age-website] via GitHub
  • Re: [I] Remove Google Tag Manager [age-website] via GitHub
• [I] How to use unwind ? [age] via GitHub
  • Re: [I] How to use unwind ? [age] via GitHub
  • Re: [I] How to use unwind ? [age] via GitHub

• Earlier messages