dev  

Messages by Thread

• • Re: [I] Performance issues with edge creation for larger dataset with 83K edges [age] via GitHub
  • Re: [I] Performance issues with edge creation for larger dataset with 83K edges [age] via GitHub
• [I] Error in interpretation of the MERGE clause [age-website] via GitHub
• [I] Is there any restriction to support for psycopg2-binary in python driver? [age] via GitHub
  • Re: [I] Is there any restriction to support for psycopg2-binary in python driver? [age] via GitHub
  • Re: [I] Is there any restriction to support for psycopg2-binary in python driver? [age] via GitHub
  • Re: [I] Is there any restriction to support for psycopg2-binary in python driver? [age] via GitHub
• Re: [I] Which quality Postgres hosts allow the AGE extension? [age] via GitHub
  • Re: [I] Which quality Postgres hosts allow the AGE extension? [age] via GitHub
  • Re: [I] Which quality Postgres hosts allow the AGE extension? [age] via GitHub
  • Re: [I] Which quality Postgres hosts allow the AGE extension? [age] via GitHub
• [PR] Bump urllib3 from 1.26.18 to 1.26.19 [age-website] via GitHub
• Re: [I] Python Driver's _nodeToJson() returns invalid JSON [age] via GitHub
  • Re: [I] Python Driver's _nodeToJson() returns invalid JSON [age] via GitHub
• Re: [I] Since there seems to be special requirements for label name, it would be nice to extend a function to verify name correctness [age] via GitHub
  • Re: [I] Since there seems to be special requirements for label name, it would be nice to extend a function to verify name correctness [age] via GitHub
  • Re: [I] Since there seems to be special requirements for label name, it would be nice to extend a function to verify name correctness [age] via GitHub
  • Re: [I] Since there seems to be special requirements for label name, it would be nice to extend a function to verify name correctness [age] via GitHub
• [I] Server crashes when using exists(path) with explicit lenght paths [age] via GitHub
  • Re: [I] Server crashes when using exists(path) with explicit lenght paths [age] via GitHub
  • Re: [I] Server crashes when using exists(path) with explicit lenght paths [age] via GitHub
  • Re: [I] Server crashes when using exists(path) with explicit lenght paths [age] via GitHub
  • Re: [I] Server crashes when using exists(path) with explicit lenght paths [age] via GitHub
  • Re: [I] Server crashes when using exists(path) with explicit lenght paths [age] via GitHub
• [PR] Update landing page and blog page [age-website] via GitHub
  • Re: [PR] Update landing page and blog page [age-website] via GitHub
• [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
  • Re: [I] SET on MERGE not storing edge properties inside the database on creation [age] via GitHub
• [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
  • Re: [I] Can we improve query performance? [age] via GitHub
• [I] GQL Support [age] via GitHub
  • Re: [I] GQL Support [age] via GitHub
  • Re: [I] GQL Support [age] via GitHub
  • Re: [I] GQL Support [age] via GitHub
• [I] Flaky test cypher_delete fails on slow machines [age] via GitHub
  • Re: [I] Flaky test cypher_delete fails on slow machines [age] via GitHub
  • Re: [I] Flaky test cypher_delete fails on slow machines [age] via GitHub
  • Re: [I] Flaky test cypher_delete fails on slow machines [age] via GitHub
• Re: [I] Compatibility Query: Running Cloned Apache Age Code on Windows OS? [age] via GitHub
  • Re: [I] Compatibility Query: Running Cloned Apache Age Code on Windows OS? [age] via GitHub
  • Re: [I] Compatibility Query: Running Cloned Apache Age Code on Windows OS? [age] via GitHub
• [PR] Bump requests from 2.31.0 to 2.32.0 [age-website] via GitHub
  • Re: [PR] Bump requests from 2.31.0 to 2.32.0 [age-website] via GitHub
• [I] Ambiguous column reference error when returning variable used in the RHS of SET clause [age] via GitHub
  • Re: [I] Ambiguous column reference error when returning variable used in the RHS of SET clause [age] via GitHub
• [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
  • Re: [I] unable to pull the docker image with 'latest' tag [age] via GitHub
• [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
  • Re: [I] Flaky test age_global_graph fails on slow machines [age] via GitHub
• Community over Code EU 2024: The countdown has started! Ryan Skraba
• [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
  • Re: [I] OLTP vs OLAP Graph Querying [age] via GitHub
• Re: [I] Union [age] via GitHub
• Re: [I] Match / Create / Set / Remove / Delete / Merge / Call / Yield Clause [age] via GitHub
• Re: [I] Fork the MariaDB Source Code [age] via GitHub
• Re: [I] Modify CREATE / SET/REMOVE / DELETE / MERGE / VLE MATCH [age] via GitHub
• Re: [I] Modify Expression logic to allow quals to work for WHERE and match constraints [age] via GitHub
• Re: [I] Modify MATCH to construct vertices and edges from custom schemas [age] via GitHub
• Re: [I] Support Table Triggers to allow the metadata tables to be updated correctly [age] via GitHub
• Re: [I] Define what metadata tables are needed to track graphids to table rows [age] via GitHub
• Re: [I] Produce a diff between the master branch and AGE for PostgreSQL 12 branch. [age] via GitHub
• Re: [I] Ensure the driver is quality controlled and secure [age] via GitHub
  • Re: [I] Ensure the driver is quality controlled and secure [age] via GitHub
  • Re: [I] Ensure the driver is quality controlled and secure [age] via GitHub
• Re: [I] Add in the Hooks to allow extension to make modifications as necessary [age] via GitHub
  • Re: [I] Add in the Hooks to allow extension to make modifications as necessary [age] via GitHub
• Re: [I] Write the extension to use those hooks [age] via GitHub
  • Re: [I] Write the extension to use those hooks [age] via GitHub
• Re: [I] Grow the community to have our changes to MariaDB necessary to do this integrated into the primary source code [age] via GitHub
  • Re: [I] Grow the community to have our changes to MariaDB necessary to do this integrated into the primary source code [age] via GitHub
• Re: [I] Create Schema Reading Tool [age] via GitHub
  • Re: [I] Create Schema Reading Tool [age] via GitHub
• Re: [I] Allow the user to customize this database to graph [age] via GitHub
  • Re: [I] Allow the user to customize this database to graph [age] via GitHub
• Re: [I] Fill out the AGE metadata tables correctly based off user mapping [age] via GitHub
  • Re: [I] Fill out the AGE metadata tables correctly based off user mapping [age] via GitHub
• Re: [I] Note that PG 12 has significant changes from PG 11. These changes need to be maintained and some code migrating from 11 will need to be adjusted to work with 12. [age] via GitHub
  • Re: [I] Note that PG 12 has significant changes from PG 11. These changes need to be maintained and some code migrating from 11 will need to be adjusted to work with 12. [age] via GitHub
• Re: [I] Incrementally migrate changes from 11 to 12. Verifying that 12 builds [age] via GitHub
  • Re: [I] Incrementally migrate changes from 11 to 12. Verifying that 12 builds [age] via GitHub
• Re: [I] Note that PG 13 has some changes from PG 12. These changes need to be maintained and some code migrating from 12 will need to be adjusted to work with 13 [age] via GitHub
  • Re: [I] Note that PG 13 has some changes from PG 12. These changes need to be maintained and some code migrating from 12 will need to be adjusted to work with 13 [age] via GitHub
• Re: [I] Map Schema to Guess of Graph the User Wants [age] via GitHub
  • Re: [I] Map Schema to Guess of Graph the User Wants [age] via GitHub
• Re: [I] Produce a diff between the experimental version of AGE for PostgreSQL 14 branch and AGE for PostgreSQL 13 branch [age] via GitHub
  • Re: [I] Produce a diff between the experimental version of AGE for PostgreSQL 14 branch and AGE for PostgreSQL 13 branch [age] via GitHub
• Re: [I] Make sure that all appropriate licenses are used, our coding standard is used, and there isn't any questionable code [age] via GitHub
  • Re: [I] Make sure that all appropriate licenses are used, our coding standard is used, and there isn't any questionable code [age] via GitHub
• Re: [I] Prerequisite: Update AGE for PostgreSQL 12 release to current [age] via GitHub
  • Re: [I] Prerequisite: Update AGE for PostgreSQL 12 release to current [age] via GitHub
• Re: [I] Produce a diff between AGE for PostgreSQL 12 branch and AGE for PostgreSQL 13 branch [age] via GitHub
  • Re: [I] Produce a diff between AGE for PostgreSQL 12 branch and AGE for PostgreSQL 13 branch [age] via GitHub
  • Re: [I] Produce a diff between AGE for PostgreSQL 12 branch and AGE for PostgreSQL 13 branch [age] via GitHub
• Re: [I] Prerequisite: Update AGE for PostgreSQL 13 release to current [age] via GitHub
  • Re: [I] Prerequisite: Update AGE for PostgreSQL 13 release to current [age] via GitHub
• Re: [I] Incrementally migrate changes from 12 to 13. Verifying that 13 builds [age] via GitHub
  • Re: [I] Incrementally migrate changes from 12 to 13. Verifying that 13 builds [age] via GitHub
• Re: [I] Note that PG 14 has some changes from PG 13. These changes need to be maintained and some code migrating from 13 will need to be adjusted to work with 14 [age] via GitHub
  • Re: [I] Note that PG 14 has some changes from PG 13. These changes need to be maintained and some code migrating from 13 will need to be adjusted to work with 14 [age] via GitHub
• Re: [I] Note that PG 14 has some changes from PG 13. These changes need to be maintained and some code migrating from 13 will need to be adjusted to work with 14. Verify this was done correctly. [age] via GitHub
  • Re: [I] Note that PG 14 has some changes from PG 13. These changes need to be maintained and some code migrating from 13 will need to be adjusted to work with 14. Verify this was done correctly. [age] via GitHub
• Re: [I] When completed, make sure any work is well documented in the commit log - including the appropriate attributions [age] via GitHub
  • Re: [I] When completed, make sure any work is well documented in the commit log - including the appropriate attributions [age] via GitHub
• Re: [I] Prerequisite: Validate the experimental AGE for PostgreSQL 14 branch's code [age] via GitHub
  • Re: [I] Prerequisite: Validate the experimental AGE for PostgreSQL 14 branch's code [age] via GitHub
• Re: [I] Perform a release [age] via GitHub
  • Re: [I] Perform a release [age] via GitHub
  • Re: [I] Perform a release [age] via GitHub
  • Re: [I] Perform a release [age] via GitHub
  • Re: [I] Perform a release [age] via GitHub
  • Re: [I] Perform a release [age] via GitHub
• Re: [I] Basic interface of the application [age] via GitHub
  • Re: [I] Basic interface of the application [age] via GitHub
  • Re: [I] Basic interface of the application [age] via GitHub
• Re: [I] Produce a diff between AGE for PostgreSQL 14 branch and AGE for PostgreSQL 13 branch [age] via GitHub
  • Re: [I] Produce a diff between AGE for PostgreSQL 14 branch and AGE for PostgreSQL 13 branch [age] via GitHub
• Re: [I] Incrementally migrate changes from 13 to 14. Verifying that 14 builds each time [age] via GitHub
  • Re: [I] Incrementally migrate changes from 13 to 14. Verifying that 14 builds each time [age] via GitHub
• Re: [I] When completed, make sure all of the migrated features and work are well documented in the commit log [age] via GitHub
  • Re: [I] When completed, make sure all of the migrated features and work are well documented in the commit log [age] via GitHub
  • Re: [I] When completed, make sure all of the migrated features and work are well documented in the commit log [age] via GitHub
  • Re: [I] When completed, make sure all of the migrated features and work are well documented in the commit log [age] via GitHub
  • Re: [I] When completed, make sure all of the migrated features and work are well documented in the commit log [age] via GitHub
  • Re: [I] When completed, make sure all of the migrated features and work are well documented in the commit log [age] via GitHub
• Re: [I] Data Modeling: Connectivity with PG/MySql [age] via GitHub
  • Re: [I] Data Modeling: Connectivity with PG/MySql [age] via GitHub
  • Re: [I] Data Modeling: Connectivity with PG/MySql [age] via GitHub
• Re: [I] Algorithms/core backend module [age] via GitHub
  • Re: [I] Algorithms/core backend module [age] via GitHub
  • Re: [I] Algorithms/core backend module [age] via GitHub
• Re: [I] Frameworks decision for backend and frontend [age] via GitHub
  • Re: [I] Frameworks decision for backend and frontend [age] via GitHub
  • Re: [I] Frameworks decision for backend and frontend [age] via GitHub
• Re: [I] Hybrid queries/Cypher queries module [age] via GitHub
  • Re: [I] Hybrid queries/Cypher queries module [age] via GitHub
  • Re: [I] Hybrid queries/Cypher queries module [age] via GitHub
• Re: [I] Creating graphs functions module [age] via GitHub
  • Re: [I] Creating graphs functions module [age] via GitHub
  • Re: [I] Creating graphs functions module [age] via GitHub
• Re: [I] Graphical query execution [age] via GitHub
  • Re: [I] Graphical query execution [age] via GitHub
  • Re: [I] Graphical query execution [age] via GitHub
• Re: [I] Graphical representation of data module [age] via GitHub
  • Re: [I] Graphical representation of data module [age] via GitHub
  • Re: [I] Graphical representation of data module [age] via GitHub
• Re: [I] Understanding Query Parsing in PgPool-II and Read/Write Split [age] via GitHub
  • Re: [I] Understanding Query Parsing in PgPool-II and Read/Write Split [age] via GitHub
  • Re: [I] Understanding Query Parsing in PgPool-II and Read/Write Split [age] via GitHub
• Re: [I] Implement Cypher Queries in Parser [age] via GitHub
  • Re: [I] Implement Cypher Queries in Parser [age] via GitHub
  • Re: [I] Implement Cypher Queries in Parser [age] via GitHub
• Re: [I] Create RHEL-8 and Rocky Linux RPMs [age] via GitHub
  • Re: [I] Create RHEL-8 and Rocky Linux RPMs [age] via GitHub
  • Re: [I] Create RHEL-8 and Rocky Linux RPMs [age] via GitHub
• Re: [I] Develop Mock Cycle [age] via GitHub
  • Re: [I] Develop Mock Cycle [age] via GitHub
• Re: [I] Back-end CRUD API integration Development [age] via GitHub
  • Re: [I] Back-end CRUD API integration Development [age] via GitHub
  • Re: [I] Back-end CRUD API integration Development [age] via GitHub
• Re: [I] ETL Function Development [age] via GitHub
  • Re: [I] ETL Function Development [age] via GitHub
  • Re: [I] ETL Function Development [age] via GitHub
• Re: [I] Based on the input parameters required to develop the following analysis module below, develop a Python module that queries arbitrary graph data, loaded in AGE, in the form of a linked list [age] via GitHub
  • Re: [I] Based on the input parameters required to develop the following analysis module below, develop a Python module that queries arbitrary graph data, loaded in AGE, in the form of a linked list [age] via GitHub
  • Re: [I] Based on the input parameters required to develop the following analysis module below, develop a Python module that queries arbitrary graph data, loaded in AGE, in the form of a linked list [age] via GitHub
• Re: [I] Define constraints that data should have to upload data analysis results to the database [age] via GitHub
  • Re: [I] Define constraints that data should have to upload data analysis results to the database [age] via GitHub

• Earlier messages
• Later messages