[GitHub] [incubator-age] aysko75 closed issue #58: Visualization tool for the AGE 0.4.0 release
aysko75 closed issue #58: URL: https://github.com/apache/incubator-age/issues/58 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] audiBookning opened a new issue #66: Formatting create graph error on duplicate
audiBookning opened a new issue #66:
URL: https://github.com/apache/incubator-age/issues/66
This issue is just to bring a minute point.
When using psql to create a graph with
```sql
SELECT create_graph('my_graph_name');
```
the return is
```sh
NOTICE: graph "my_graph_name" has been created
```
But when the graph is a duplicate the error given is
```sh
ERROR: schema "my_graph_name" already exists
```
I was thinking that this message comes probably from postgresql and is not
directly controlled by AGE?
Since we are using a AGE function, maybe we should be getting an error
similar to:
```sh
ERROR: graph "my_graph_name" already exists
```
This would help to emphasize the idea that a graph is much more than a
schema and to use the AGE functions instead of, for a stretched example, trying
to artificially delete a graph by deleting the schema.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] audiBookning opened a new issue #67: PSQL recreates a graph that was already created with PG
audiBookning opened a new issue #67:
URL: https://github.com/apache/incubator-age/issues/67
I encountered a strange situation when doing some experiments with AGE.
I used node-postgres (pg) to create a graph with
```sql
SELECT create_graph('my_graph_name');
```
if i repeat the same query, i will correctly get an error
```sh
ERROR: schema "my_graph_name" already exists
```
But if afterward i use psql to repeat the query, i get
```sh
NOTICE: graph "my_graph_name2" has been created
```
repeating it a 2º time in psql (or in pg) with gives the correct error.
I would expect to get an error, the first time, when trying the query in
psql since i already created the graph in pg.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #67: PSQL recreates a graph that was already created with PG
JoshInnis commented on issue #67: URL: https://github.com/apache/incubator-age/issues/67#issuecomment-839936231 It appears in the psql session you added a '2' to the graph name. Whereas in node-postgres you created a graph called 'my_graph_name'. Without seeing your scripts I cannot be sure, but it appears the reason why it was successful was because you used a different name. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] audiBookning commented on issue #67: PSQL recreates a graph that was already created with PG
audiBookning commented on issue #67: URL: https://github.com/apache/incubator-age/issues/67#issuecomment-840129518 I am sorry. The 2 is an artifact of copying the code to the issue. I made another test with the 2 added to the end of the graph name to confirm the behaviour and when copying the code i forgot to remove it. 😪 I mean that the 2 in this case is not relevant to the issue. I will edit the main issue to remove it. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] audiBookning edited a comment on issue #67: PSQL recreates a graph that was already created with PG
audiBookning edited a comment on issue #67: URL: https://github.com/apache/incubator-age/issues/67#issuecomment-840129518 I am sorry. The 2 is an artifact of copying the code to the issue. I made another test with the 2 added to the end of the graph name to confirm the behaviour and when copying the code i forgot to remove it. 😪 TLTR: the 2 in this case is not relevant to the issue. I will edit the main issue to remove it. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age-website] aysko75 opened a new pull request #11: Apache age website branch by ak
aysko75 opened a new pull request #11: URL: https://github.com/apache/incubator-age-website/pull/11 Roadmap updated -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age-website] eyab merged pull request #11: Apache age website branch by ak
eyab merged pull request #11: URL: https://github.com/apache/incubator-age-website/pull/11 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] jrgemignani closed issue #64: explain execution plan display
jrgemignani closed issue #64: URL: https://github.com/apache/incubator-age/issues/64 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age-website] aysko75 opened a new pull request #12: Apache age website branch by ak
aysko75 opened a new pull request #12: URL: https://github.com/apache/incubator-age-website/pull/12 fixed the errors -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] kysmou commented on issue #65: Apply bind variable to cypher
kysmou commented on issue #65:
URL: https://github.com/apache/incubator-age/issues/65#issuecomment-841903602
To test the prepared statement, I tested it by referring to the manual.
However, the following error occurs, but if there is something I am doing
wrong, please tell me. This is the age 0.4.0 version.
PREPARE cypher_stored_procedure(agtype) AS
SELECT *
FROM cypher('test_graph', $$
MATCH (v:Person)
WHERE v.name = $name
RETURN v
$$, $1)
AS (v agtype);
execute cypher_prepared_statement('{"name":"affeee"}');
ERROR: prepared statement "cypher_prepared_statement" does not exist
STATEMENT: execute cypher_prepared_statement('{"name":"affeee"}');
prepared statement "cypher_prepared_statement" does not exist
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] kysmou commented on issue #65: Apply bind variable to cypher
kysmou commented on issue #65:
URL: https://github.com/apache/incubator-age/issues/65#issuecomment-841903602
To test the prepared statement, I tested it by referring to the manual.
However, the following error occurs, but if there is something I am doing
wrong, please tell me. This is the age 0.4.0 version.
PREPARE cypher_stored_procedure(agtype) AS
SELECT *
FROM cypher('test_graph', $$
MATCH (v:Person)
WHERE v.name = $name
RETURN v
$$, $1)
AS (v agtype);
execute cypher_prepared_statement('{"name":"affeee"}');
ERROR: prepared statement "cypher_prepared_statement" does not exist
STATEMENT: execute cypher_prepared_statement('{"name":"affeee"}');
prepared statement "cypher_prepared_statement" does not exist
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age-website] eyab merged pull request #12: Apache age website branch by ak
eyab merged pull request #12: URL: https://github.com/apache/incubator-age-website/pull/12 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] pdpotter commented on issue #45: unique properties / indexing
pdpotter commented on issue #45:
URL: https://github.com/apache/incubator-age/issues/45#issuecomment-845153669
I tried using id() instead of using properties for matching, but this was
even slower (I noticed using an additional `WHERE` clause instead of defining
properties in the `MATCH` clause is slower in another use case as well).
For this, I rewrote
```
SELECT * FROM cypher('graph_name', $$
MATCH (d:LabelA {id: 1}), (r:LabelB {id: 2})
CREATE (d)-[:Relation {prop: 'value'}]->(r)
$$) as (a agtype);
```
to
```
SELECT * FROM cypher('graph_name', $$
MATCH (d:LabelA), (r:LabelB)
WHERE id(d) = 1 and id(r) = 2
CREATE (d)-[:Relation {prop: 'value'}]->(r)
$$) as (a agtype);
```
where I obtained the ids (the ones above are made up) using
```
SELECT * FROM cyper('graph_name',$$
MATCH (n:LabelA)
return id(n), n.id
$$) as (id agtype, prop agtype);
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw opened a new issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
seo-kw opened a new issue #75:
URL: https://github.com/apache/incubator-age/issues/75
Well, It's a kind of silly thing. And not a bug in AGE. But who is a
newcomer, like me, maybe helpful information.
Maybe we'll test some queries in the official pdf guide through opened
browser, but some troubles in a specific browser which is firefox.
If you just copy & paste below query throughout browser, like this query,
maybe you've got some error like this
Query : SELECT​ *FROM​ cypher(​'graph_name'​, $$​CREATE​ (n), (m)$$) ​as​ (v
agtype);
1. ERROR: syntax error at or near "SELECT​"
2. ERROR: cache lookup failed for type 0 at character 28
I got some errors like these. I found nothing helpful and why these errors
i've gotten.
The reason was that you copy query, just got extended-ASCII code together.
firefox copy-paste
1. query: SELECT​ * FROM​ cypher(​'a'​, $$​ CREATE​ (n), (m) $$ ) ​as​ (v
agtype);
2. hex : 53 45 4c 45 43 54 **e2 80 8b** 20 2a 20 46 52 4f 4d **e2 80 8b** 20
63 79 70 68 65 72 28 **e2 80 8b** 27 61 27 **e2 80 8b** 2c 20 24 24 **e2 80
8b** 20 43 52 45 41 54 45 **e2 80 8b** 20 28 6e 29 2c 20 28 6d 29 20 24 24 20
29 20 **e2 80 8b** 61 73 **e2 80 8b** 20 28 76 20 61 67 74 79 70 65 29 3b
other browsers copy-paste
1. query: SELECT *
FROM cypher('graph_name', $$
CREATE (n), (m)
$$) as (v agtype);
2. hex : 53 45 4c 45 43 54 20 2a 0d 0a 46 52 4f 4d 20 63 79 70 68 65 72 28
27 67 72 61 70 68 5f 6e 61 6d 65 27 2c 20 24 24 0d 0a 43 52 45 41 54 45 20 28
6e 29 2c 20 28 6d 29 0d 0a 24 24 29 20 61 73 20 28 76 20 61 67 74 79 70 65 29 3b
The error point is "**e2 80 8b**" hex code which means "ZERO WIDTH SPACE".
You can see that at [utf-8
chart](https://www.utf8-chartable.de/unicode-utf8-table.pl?start=8192&number=128)
Oh well, I just too much talk about this.
Maybe adding browser recommendations will avoid what have I done.
I just say, In short, do not copy queries Apache_AGE_Guide.pdf on firefox!
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw opened a new issue #76: preparestatement supporting issues(?)
seo-kw opened a new issue #76:
URL: https://github.com/apache/incubator-age/issues/76
Hello there, I got some trouble in using JDBC preparestatement. So I want to
share about my experiences.
I have been confused rather am I doing something wrong or is it a bug. So, I
just write down those phenomena.
1. Querystring
1. PrepareStatement
```java
PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
"select * from cypher('a', $$ "+
"match (a) where id(a) = ? return properties(a)" +
"$$) as (a agtype););"
pstmt.setString(1, "281474976710667"); //character '?' is replaced to
281474976710667
```
2. Prepared Statements Preparation & Execution in "Apache_AGE_Guide.pdf"
```java
PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
"PREPARE cypher_stored_procedure(agtype) AS " +
"select * " +
"from cypher('a', $$ " +
"match (a) " +
"where a.id = $id " +
"return properties(a) " +
"$$, $1) as (a agtype);" +
"EXECUTE cypher_stored_procedure(('{\"id\": \"
? \"}'))");
pstmt.setString(1, "844424930131976"); // character '?' is replaced
to 844424930131976
```
2. Error message
Both of them got the same out of index error. because they aren't
replaced to other strings which is what we want to replace.
(org.postgresql.util.PSQLException: The column index is out of range: 1, number
of columns: 0.)
3. Suggestion
I asked about these errors to a coworker and understood why those errors
were thrown. Because of accurate error showing, you guys did so.
I concluded dollar-quoted strings are not to be replaced now. But JDBC
standards compatibility is a kind of important thing about normal users. And
AGE is an extension of Postgres. So how about some another route about
preparestatement supporting?
4. Conclusion
I am waiting for your opinion. or maybe you want some specific things
about this article. then, feel easy to tell me. I would happily append more
detailed info.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] pdpotter commented on issue #76: Preparestatement supporting issues(?)
pdpotter commented on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850207557
I haven't used JDBC myself, but if it is similar to asyncpg, it should work
like this:
```
PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
"select * from cypher('a', $$ "+
"match (a) where id(a) = $id return properties(a)" +
"$$, ?) as (a agtype););"
pstmt.setString(1, '{\"id\": 281474976710667}');
```
Additional remark: `id(a)` (automatically generated primary key for the
vertex a) is not the same as `a.id` (property id of the vertex a).
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #76: Preparestatement supporting issues(?)
seo-kw commented on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850256389
>
>
> I haven't used JDBC myself, but if it is similar to asyncpg, it should
work like this:
>
> ```
> PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
>"select * from cypher('a', $$ "+
>"match (a) where id(a) = $id return properties(a)" +
>"$$, ?) as (a agtype););"
> pstmt.setString(1, '{\"id\": 281474976710667}');
> ```
>
> Additional remark: `id(a)` (automatically generated primary key for the
vertex a) is not the same as `a.id` (property id of the vertex a).
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw closed issue #76: Preparestatement supporting issues(?)
seo-kw closed issue #76: URL: https://github.com/apache/incubator-age/issues/76 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw removed a comment on issue #76: Preparestatement supporting issues(?)
seo-kw removed a comment on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850256389
>
>
> I haven't used JDBC myself, but if it is similar to asyncpg, it should
work like this:
>
> ```
> PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
>"select * from cypher('a', $$ "+
>"match (a) where id(a) = $id return properties(a)" +
>"$$, ?) as (a agtype););"
> pstmt.setString(1, '{\"id\": 281474976710667}');
> ```
>
> Additional remark: `id(a)` (automatically generated primary key for the
vertex a) is not the same as `a.id` (property id of the vertex a).
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #76: Preparestatement supporting issues(?)
seo-kw commented on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850272683
>
>
> I haven't used JDBC myself, but if it is similar to asyncpg, it should
work like this:
>
> ```
> PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
>"select * from cypher('a', $$ "+
>"match (a) where id(a) = $id return properties(a)" +
>"$$, ?) as (a agtype););"
> pstmt.setString(1, '{\"id\": 281474976710667}');
> ```
>
> Additional remark: `id(a)` (automatically generated primary key for the
vertex a) is not the same as `a.id` (property id of the vertex a).
Hi potter. I just closed this issue by mistake. Sorry for the confusion. And
thanks for your reply.
But I didn't solve the previous problem you suggested.
I just applied your solution below.
```
PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
"select * from cypher('a', $$ "+
"match (a) where a.id = $id return properties(a)" +
"$$, ?) as (a agtype););");
pstmt.setString(1, "{\"id\": 281474976710667}");
```
I check this syntax in AGE_Guide.pdf "Prepared Statements" paragraph. and
maybe I know what you meant to.
but I got errors below.
`
org.postgresql.util.PSQLException: ERROR: function cypher(unknown, unknown,
character varying) does not exist
Hint: No function matches the given name and argument types. You might
need to add explicit type casts.
`
Maybe character '?' is recognized to character varying and it's not accepted
in function.
Anyway, I appreciate your feedback.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw edited a comment on issue #76: Preparestatement supporting issues(?)
seo-kw edited a comment on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850272683
>
>
> I haven't used JDBC myself, but if it is similar to asyncpg, it should
work like this:
>
> ```
> PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
>"select * from cypher('a', $$ "+
>"match (a) where id(a) = $id return properties(a)" +
>"$$, ?) as (a agtype););"
> pstmt.setString(1, '{\"id\": 281474976710667}');
> ```
>
> Additional remark: `id(a)` (automatically generated primary key for the
vertex a) is not the same as `a.id` (property id of the vertex a).
Hi potter. I just closed this issue by mistake. Sorry for the confusion. And
thanks for your reply.
But I didn't solve the previous problem through your solution that you
suggested.
I just applied your solution below.
```
PreparedStatement pstmt =
connectionHelper.createConnection().prepareStatement(
"select * from cypher('a', $$ "+
"match (a) where a.id = $id return properties(a)" +
"$$, ?) as (a agtype););");
pstmt.setString(1, "{\"id\": 281474976710667}");
```
I check this syntax in AGE_Guide.pdf "Prepared Statements" paragraph. and
maybe I know what you meant to.
but I got errors below.
`
org.postgresql.util.PSQLException: ERROR: function cypher(unknown, unknown,
character varying) does not exist
Hint: No function matches the given name and argument types. You might
need to add explicit type casts.
`
Maybe character '?' is recognized to character varying and it's not accepted
in function.
Anyway, I appreciate your feedback.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] pdpotter commented on issue #76: Preparestatement supporting issues(?)
pdpotter commented on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850282617
Did you execute `LOAD 'age';` and `SET search_path = ag_catalog, "$user",
public;` on your connection before executing the query above?
Probably something like this (again, I haven't tried this and I am not
familiar with JDBC):
```
Connection conn = connectionHelper.createConnection();
Statement loadStatement = conn.createStatement();
statement.execute("LOAD 'age'");
statement.execute("SET search_path = ag_catalog, \"$user\", public;");
PreparedStatement pstmt = conn.prepareStatement(
"select * from cypher('a', $$ "+
"match (a) where a.id = $id return properties(a)" +
"$$, ?) as (a agtype););");
pstmt.setString(1, "{\"id\": 281474976710667}");
ResultSet resultset = pstmt.executeQuery();
conn.close();
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #76: Preparestatement supporting issues(?)
seo-kw commented on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850390215
>
>
> Did you execute `LOAD 'age';` and `SET search_path = ag_catalog, "$user",
public;` on your connection before executing the query above?
>
> Probably something like this (again, I haven't tried this and I am not
familiar with JDBC):
>
> ```
> Connection conn = connectionHelper.createConnection();
>
> Statement loadStatement = conn.createStatement();
> statement.execute("LOAD 'age'");
> statement.execute("SET search_path = ag_catalog, \"$user\", public;");
>
> PreparedStatement pstmt = conn.prepareStatement(
> "select * from cypher('a', $$ "+
> "match (a) where a.id = $id return properties(a)" +
> "$$, ?) as (a agtype););");
> pstmt.setString(1, "{\"id\": 281474976710667}");
> ResultSet resultset = pstmt.executeQuery();
> conn.close();
> ```
Hello again. Wow, thanks for the fast reply! I got dinner so am quite late
lol.
Then, sure. It's a kind of basic process to using age.
I did that process in another class. and like this.
```
Statement statement = connection.createStatement();
statement.execute("CREATE EXTENSION IF NOT EXISTS age;");
statement.execute("LOAD 'age';");
statement.execute("set search_path = a, ag_catalog, \"$user\",
public");
```
And also created graph using `SELECT create_graph('a')` function.
You're not familiar with jdbc but you've done this for me. Thanks a lot. But
I supposed to it's kind of AGE's core architectural algorithm problem.
No offense, If I am something wrong, feel free to tell me then, I would be
happy.
It's almost the weekend, have a nice week guys.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] seo-kw edited a comment on issue #76: Preparestatement supporting issues(?)
seo-kw edited a comment on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850390215
>
>
> Did you execute `LOAD 'age';` and `SET search_path = ag_catalog, "$user",
public;` on your connection before executing the query above?
>
> Probably something like this (again, I haven't tried this and I am not
familiar with JDBC):
>
> ```
> Connection conn = connectionHelper.createConnection();
>
> Statement loadStatement = conn.createStatement();
> statement.execute("LOAD 'age'");
> statement.execute("SET search_path = ag_catalog, \"$user\", public;");
>
> PreparedStatement pstmt = conn.prepareStatement(
> "select * from cypher('a', $$ "+
> "match (a) where a.id = $id return properties(a)" +
> "$$, ?) as (a agtype););");
> pstmt.setString(1, "{\"id\": 281474976710667}");
> ResultSet resultset = pstmt.executeQuery();
> conn.close();
> ```
Hello again. Wow, thanks for the fast reply! I got dinner so am quite late
lol.
Then, sure. It's a kind of basic process to using age.
I did that process in another class. and like this.
```
Statement statement = connection.createStatement();
statement.execute("CREATE EXTENSION IF NOT EXISTS age;");
statement.execute("LOAD 'age';");
statement.execute("set search_path = a, ag_catalog, \"$user\",
public");
```
And also created graph using `SELECT create_graph('a')` function.
You're not familiar with jdbc but you've done this for me. Thanks a lot. But
I supposed to it's kind of AGE's core architectural algorithm problem.
No offense, If I am something wrong, feel free to tell me then, I would be
happy.
It's almost the weekend, have a nice weekend guys.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] pdpotter commented on issue #76: Preparestatement supporting issues(?)
pdpotter commented on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850392760 Are you using this same connection object to execute the match query? In my asyncpg code, I have to make sure `LOAD 'age';` and `set search_path = a, ag_catalog, \"$user\", public` are executed on the connection object that is used to do actual age queries. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #76: Preparestatement supporting issues(?)
seo-kw commented on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850412218 > > > Are you using this same connection object to execute the match query? > > In my asyncpg code, I have to make sure `LOAD 'age';` and `set search_path = a, ag_catalog, \"$user\", public` are executed on the connection object that is used to do actual age queries. Yes. I'm using the same connection object. I have tested many functions in [http://age.incubator.apache.org/docs/Apache_AGE_Guide.pdf](http://age.incubator.apache.org/docs/Apache_AGE_Guide.pdf) through that connection. For example, basic graph creation and delete, update, and so on. But I got stuck in preparestatement in jdbc. That's the reason that I made this issue. Anyway, I'm thanks for the continuous reply <3 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw edited a comment on issue #76: Preparestatement supporting issues(?)
seo-kw edited a comment on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-850412218 > > > Are you using this same connection object to execute the match query? > > In my asyncpg code, I have to make sure `LOAD 'age';` and `set search_path = a, ag_catalog, \"$user\", public` are executed on the connection object that is used to do actual age queries. Yes. I'm using the same connection object. I have tested many functions in [http://age.incubator.apache.org/docs/Apache_AGE_Guide.pdf](http://age.incubator.apache.org/docs/Apache_AGE_Guide.pdf) through that connection. For example, basic graph creation and delete, update, and so on. But I got stuck in preparestatement in jdbc. That's the reason that I made this issue. Anyway, I'm thanks for the your continuous reply <3 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw opened a new issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
seo-kw opened a new issue #79:
URL: https://github.com/apache/incubator-age/issues/79
### Assigning in edge to vertex label.
```
SELECT * FROM cypher('a', $$
MATCH (b), (c)
WHERE id(b) = 4222124650659842 and id(c) = 4222124650659843
CREATE (b)-[a: already_created_vertex_label_name { name:'abc'}]->(c)
return id(a)
$$) as (a agtype);
```
### Assigning in vertex to edge label.
```
SELECT * FROM cypher('a', $$
create (a: already_created_edge_label_name { name:'abc'})
return id(a)
$$) as (a agtype);
```
Both of them, print "[08006] An I/O error occurred while sending to the
backend. java.io.EOFException".
I think.. some error handling logics or guidance help in using ages much
better.
Thanks for reading and have a nice day.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #65: Apply bind variable to cypher
JoshInnis commented on issue #65: URL: https://github.com/apache/incubator-age/issues/65#issuecomment-854869456 In the second example, the prepared statement is called "cypher_stored_procedure" and the execute is for the prepared statement "cypher_prepared_statement." -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] bionicles commented on issue #49: Please document a rust client
bionicles commented on issue #49: URL: https://github.com/apache/incubator-age/issues/49#issuecomment-855377659 Cool, just mean to say, any easy ways to get a cloud hosted AGE service running, could definitely help newcomers feel more confident in the project -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] bionicles edited a comment on issue #49: Please document a rust client
bionicles edited a comment on issue #49: URL: https://github.com/apache/incubator-age/issues/49#issuecomment-855377659 Cool, just mean to say, any easy ways to get a cloud hosted AGE service running, could definitely help newcomers feel more confident in the project (and perhaps fund it!) -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] joefagan commented on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
joefagan commented on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-855943349 FYI AgensGraph 2.1.2 returns these errors respectively ERROR: label "already_created_edge_label_name" is edge label and ERROR: label "already_created_vertex_label_name" is edge label -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw closed issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
seo-kw closed issue #79: URL: https://github.com/apache/incubator-age/issues/79 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
seo-kw commented on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-856328136 Thanks for the reference info, Joe. > > > FYI AgensGraph 2.1.2 returns these errors respectively > ERROR: label "already_created_edge_label_name" is edge label > and > ERROR: label "already_created_vertex_label_name" is edge label -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
seo-kw commented on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-856328497 Thanks for the reference info, Joe. Oh.. I closed again of mistake. sry, Reopened. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw edited a comment on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
seo-kw edited a comment on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-856328497 Thanks for the reference info, Joe. Oh.. I closed again by mistake. sry, Reopened. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw edited a comment on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
seo-kw edited a comment on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-856328497 Oh.. I closed again by mistake. sry, Reopened. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug commented on issue #76: Preparestatement supporting issues(?)
emotionbug commented on issue #76:
URL: https://github.com/apache/incubator-age/issues/76#issuecomment-856354546
I test some cases for using prepared statement.
**case-1**
```pgsql
-- case#1 with agtype_build_map func
select * from cypher('age', $$ MATCH (n) WHERE n.released = $released RETURN
n $$, agtype_build_map('released', '1999')) as (n agtype);
-- ERROR: third argument of cypher function must be a parameter
```
https://github.com/apache/incubator-age/blob/83426d3a92bd5fee06376a38542d35efb1e6397b/src/backend/parser/cypher_analyze.c#L348-L354
it looks like bug.
**case-2**
```pgsql
-- case#2 with none dollar quoted string
select * from cypher('age', concat('MATCH (n) RETURN ', 'n')::cstring) as (n
agtype);
-- ERROR: a dollar-quoted string constant is expected
```
https://github.com/apache/incubator-age/blob/83426d3a92bd5fee06376a38542d35efb1e6397b/src/backend/parser/cypher_analyze.c#L319-L340
This seems to exist to accurately mark the syntax problem, and I think it
would be better to give the user an option.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo opened a new issue #84: WHERE syntax doesn't seem to work
songololo opened a new issue #84:
URL: https://github.com/apache/incubator-age/issues/84
I'm trying to do a relatively basic MATCH with a WHERE clause but I keep
encountering an error per:
```
ERROR: operator is not unique: ag_catalog.agtype = ag_catalog.agtype
Hint: Could not choose a best candidate operator. You might need to add
explicit type casts. Position: 93
```
The item and its item property exists in the graph.
This is the query:
```postgresql
SELECT *
FROM ag_catalog.cypher('my_test_graph', $$
MATCH (n:some_label)
WHERE n.pkey = 'some123string456'
RETURN n.pkey
$$) as (v ag_catalog.agtype);
```
Where `some_label` and `some123string456` correspond to the vertex labels
and properties in the graph.
The `pkey` property is stored as a string.
I've tried adding explicit type casts, e.g. ::text and ::char but these
return the following errors:
```
ERROR: typecast 'text' not supported
```
When I reframe the query per:
```
SELECT *
FROM ag_catalog.cypher('my_test_graph', $$
MATCH (n:some_label {pkey: 'some123string456'})
RETURN n.pkey
$$) as (v ag_catalog.agtype);
```
then it works.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] jrgemignani commented on issue #84: WHERE syntax doesn't seem to work
jrgemignani commented on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857199330
What version are you using? This is from the latest pull of the master on
github -
```
psql-11.5-5432-pgsql=# SELECT * FROM cypher('G', $$CREATE (:begin {name :
'John'})-[:edge1 {name: '1'}]->(:middle)-[:edge1 {name:
'2'}]->(:middle)-[:edge2 {name: '1'}]->(:middle)-[:edge2 {name: '2'}]->(:end)
$$) AS (a agtype); a
---
(0 rows)
psql-11.5-5432-pgsql=# SELECT * FROM ag_catalog.cypher('G', $$ MATCH
(n:begin {name: 'John'}) WHERE n.name = 'John' RETURN n $$) as (v agtype);
v
---
{"id": 844424931131979, "label": "begin", "properties": {"name":
"John"}}::vertex
(1 row)
psql-11.5-5432-pgsql=# SELECT * FROM ag_catalog.cypher('G', $$ MATCH
(n:begin {name: 'John'}) WHERE n.name = 'John' RETURN n.name $$) as (v agtype);
v
"John"
(1 row)
psql-11.5-5432-pgsql=#
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #76: Preparestatement supporting issues(?)
JoshInnis commented on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-857261677 @pdpotter @seo-kw Agtype is an extensible type in Postgres. The standard JDBC driver does not support it. In the driver folder for the repository there is an extension to the JDBC driver that should support using Agtype in Java. https://github.com/apache/incubator-age/tree/master/drivers/jdbc @emotionbug The third argument of the Cypher can only be not NULL when used with prepared statements. Otherwise an error will be thrown. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug commented on issue #76: Preparestatement supporting issues(?)
emotionbug commented on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-857279217 @JoshInnis Uhm... can you explain why? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug edited a comment on issue #76: Preparestatement supporting issues(?)
emotionbug edited a comment on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-857279217 @JoshInnis Uhm... colud you explain why can't use without prepared statements? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug edited a comment on issue #76: Preparestatement supporting issues(?)
emotionbug edited a comment on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-857279217 @JoshInnis Uhm... could you explain why can't use without prepared statements? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug opened a new issue #85: project build problem( make -j option .., bison dependency )
emotionbug opened a new issue #85:
URL: https://github.com/apache/incubator-age/issues/85
when use make with -j option like `make -j16` throws error with
`cypher_gram_def.h`
```
src/backend/parser/cypher_gram.c:147:10: fatal error: cypher_gram_def.h: no
such file or directory
147 | #include "cypher_gram_def.h"
| ^~~
```
it seems trying to compile, before bison generate codes.
so, how about change `Makefile` like behind?
PS, looks like bison not generating with directory part prefix after Bison
3.7.
so, I added `CPPFLAGS` for include header without prefix.
`PG_CPPFLAGS = -I$(ag_include_dir) -I$(ag_include_dir)/parser`
I don't think this is a good way. therefore, how about giving options
according to the version.
`Directive: %define api.header.include {"header.h"}`
https://www.gnu.org/software/bison/manual/html_node/_0025define-Summary.html
```diff
74c74
< cypher_delete \
---
> cypher_delete \
82c82
< EXTRA_CLEAN = $(addprefix $(ag_regress_dir)/, $(ag_regress_out))
---
> EXTRA_CLEAN = $(addprefix $(ag_regress_dir)/, $(ag_regress_out))
src/backend/parser/cypher_gram.c src/include/parser/cypher_gram_def.h
85c85
< PG_CPPFLAGS = -I$(ag_include_dir)
---
> PG_CPPFLAGS = -I$(ag_include_dir) -I$(ag_include_dir)/parser
91c91,96
< src/backend/parser/cypher_gram.c: BISONFLAGS +=
--defines=$(ag_include_dir)/parser/$(basename $(notdir $@))_def.h
---
> src/include/parser/cypher_gram_def.h: src/backend/parser/cypher_gram.c
>
> src/backend/parser/cypher_gram.c: BISONFLAGS +=
--defines=src/include/parser/cypher_gram_def.h
>
> src/backend/parser/cypher_parser.o: src/backend/parser/cypher_gram.c
> src/backend/parser/cypher_keywords.o: src/backend/parser/cypher_gram.c
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo commented on issue #84: WHERE syntax doesn't seem to work
songololo commented on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857497693
If I build a docker image from the main branch and run the following::
```
SELECT *
FROM ag_catalog.drop_graph('threeds', True);
SELECT *
FROM ag_catalog.create_graph('threeds');
SELECT *
FROM ag_catalog.cypher('threeds', $$
CREATE (:begin {name : 'John'})-[:edge1 {name: '1'}]->(:middle)-[:edge1
{name: '2'}]->(:end)
$$) AS (a ag_catalog.agtype);
SELECT *
FROM ag_catalog.cypher('threeds', $$
MATCH (n:begin {name: 'John'})
WHERE n.name = 'John'
RETURN n
$$) as (v ag_catalog.agtype);
```
Then I'm encountering:
```
ERROR: operator is not unique: ag_catalog.agtype = ag_catalog.agtype
Hint: Could not choose a best candidate operator. You might need to add
explicit type casts.
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo edited a comment on issue #84: WHERE syntax doesn't seem to work
songololo edited a comment on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857497693
If I build a docker image from the main branch and run the following::
```
SELECT *
FROM ag_catalog.drop_graph('threeds', True);
SELECT *
FROM ag_catalog.create_graph('threeds');
SELECT *
FROM ag_catalog.cypher('threeds', $$
CREATE (:begin {name : 'John'})-[:edge1 {name: '1'}]->(:middle)-[:edge1
{name: '2'}]->(:end)
$$) AS (a ag_catalog.agtype);
SELECT *
FROM ag_catalog.cypher('threeds', $$
MATCH (n:begin {name: 'John'})
WHERE n.name = 'John'
RETURN n
$$) as (v ag_catalog.agtype);
```
Then I'm encountering:
```
ERROR: operator is not unique: ag_catalog.agtype = ag_catalog.agtype
Hint: Could not choose a best candidate operator. You might need to add
explicit type casts.
```
This is my Dockerfile:
```
FROM postgis/postgis:11-3.1-alpine
# RUN apk add --no-cache postgresql-dev=11.10-r0
#postgresql-plpython2=11.10-r0
--repository=http://dl-cdn.alpinelinux.org/alpine/v3.9/main
RUN apk add --no-cache \
bison=3.6.2-r0 \
flex=2.6.4-r2 \
g++=9.3.0-r2 \
--repository=http://dl-cdn.alpinelinux.org/alpine/v3.12/main
RUN apk add --no-cache \
clang \
flex \
git \
llvm \
make
RUN git clone --depth 1 https://github.com/apache/incubator-age /age
RUN cd /age && make install
RUN ln -s /usr/lib/postgresql/plpython2.so
/usr/local/lib/postgresql/plpython2.so \
&& ln -s /usr/share/postgresql/extension/plpython2u.control
/usr/local/share/postgresql/extension/plpythonu.control \
&& ln -s /usr/share/postgresql/extension/plpython2u--1.0.sql
/usr/local/share/postgresql/extension/plpythonu--1.0.sql \
&& ln -s /usr/share/postgresql/extension/plpython2u--unpackaged--1.0.sql
/usr/local/share/postgresql/extension/plpythonu--unpackaged--1.0.sql
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] kysmou closed issue #57: First cypher execution error after alter database set search_path statement
kysmou closed issue #57: URL: https://github.com/apache/incubator-age/issues/57 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] songololo commented on issue #84: WHERE syntax doesn't seem to work
songololo commented on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857594546
OK, interesting, if I run:
```
LOAD 'age';
SET search_path = ag_catalog, "$user", public;
```
Then:
```
SELECT *
FROM cypher('test', $$
MATCH (n:begin {name: 'John'})
WHERE n.name = 'John'
RETURN n
$$) as (n agtype);
```
Then it works as intended.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo closed issue #84: WHERE syntax doesn't seem to work
songololo closed issue #84: URL: https://github.com/apache/incubator-age/issues/84 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] songololo edited a comment on issue #84: WHERE syntax doesn't seem to work
songololo edited a comment on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857604398
For others running into this, a solution is to add the "search_path" to your
connection settings:
```
await asyncpg.create_pool(**self.db_config,
server_settings={'search_path':
'ag_catalog, "$user", public'},
min_size=1,
max_size=3)
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo commented on issue #84: WHERE syntax doesn't seem to work
songololo commented on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857604398
For others running into this, a solution is to add the "search_path" to your
connection settings:
```
await asyncpg.create_pool(**self.db_config,
server_settings={'search_path': 'ag_catalog, "$user", public'},
min_size=1,
max_size=3)
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo edited a comment on issue #84: WHERE syntax doesn't seem to work
songololo edited a comment on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857604398
For others running into this, a solution is to add the "search_path" to your
connection settings:
```
await asyncpg.create_pool(**self.db_config,
server_settings={'search_path': 'ag_catalog, "$user", public'},
min_size=1,
max_size=3)
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo edited a comment on issue #84: WHERE syntax doesn't seem to work
songololo edited a comment on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857604398
For others running into this, a solution is to add the "search_path" to your
connection settings:
```
await asyncpg.create_pool(**self.db_config, server_settings={'search_path':
'ag_catalog, "$user", public'},)
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo edited a comment on issue #84: WHERE syntax doesn't seem to work
songololo edited a comment on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857604398
For others running into this, a solution is to add the "search_path" to your
connection settings, e.g. for `asyncpg`:
```
await asyncpg.create_pool(**self.db_config, server_settings={'search_path':
'ag_catalog, "$user", public'},)
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] songololo edited a comment on issue #84: WHERE syntax doesn't seem to work
songololo edited a comment on issue #84:
URL: https://github.com/apache/incubator-age/issues/84#issuecomment-857604398
For others running into this, a solution is to add the "search_path" to your
connection settings, e.g. for `asyncpg`:
```
await asyncpg.create_pool(**self.db_config,
server_settings={'search_path': 'ag_catalog, "$user", public'})
```
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis closed issue #47: Examples of how to join relational data
JoshInnis closed issue #47: URL: https://github.com/apache/incubator-age/issues/47 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #76: Preparestatement supporting issues(?)
JoshInnis commented on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-859957803 @emotionbug I'm not sure what you're asking. You can use AGE in Java without using Prepared Statements. However, the JDBC driver cannot parse Agtype correctly. You would need the need the extension to the JDBC driver located in this repository. Since prepared statements use Agtype to pass the parameters, you cannot use prepared statements with AGE without the driver extension. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug edited a comment on issue #76: Preparestatement supporting issues(?)
emotionbug edited a comment on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-860228285 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug commented on issue #76: Preparestatement supporting issues(?)
emotionbug commented on issue #76: URL: https://github.com/apache/incubator-age/issues/76#issuecomment-860228285 @JoshInnis I mean, I wonder why can't use the parameter value if don't use PreparedStatement. ``` An optional map of parameters used for stored procedure. Default is NULL. See Stored Procedures for details ``` and, read the document, but I think there is a way to support it even if it is not functionally stored procedures, and I hope this function is supported for general situation, not PreparedStatement. Because, I think can make a more readable query using this function. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] joefagan commented on issue #67: PSQL recreates a graph that was already created with PG
joefagan commented on issue #67: URL: https://github.com/apache/incubator-age/issues/67#issuecomment-860821357 Please post your config to make sure we're pointing at the same server and same database when trying to recreating the graph. . -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #52: exists `label(...)` function in AGE?
JoshInnis commented on issue #52: URL: https://github.com/apache/incubator-age/issues/52#issuecomment-860827312 That is the plan. Label Inheritance is not currently implemented. But we have that on the backlog and the plan is for that function to return it's label all labels it inherits. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] leonh commented on issue #85: project build problem( make -j option .., bison dependency )
leonh commented on issue #85: URL: https://github.com/apache/incubator-age/issues/85#issuecomment-860926197 Experienced this exact issue following the source install steps in the documentation on the Ubuntu 21.4 , which installs Bison 3.7.5 . Altering the line in the Makefile to: PG_CPPFLAGS = -I$(ag_include_dir) -I$(ag_include_dir)/parser solved the problem for me -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] leonh edited a comment on issue #85: project build problem( make -j option .., bison dependency )
leonh edited a comment on issue #85: URL: https://github.com/apache/incubator-age/issues/85#issuecomment-860926197 Experienced this exact issue following the source install steps in the documentation on Ubuntu 21.4 , (on which apt-get installs Bison 3.7.5 ) Altering the line in the Makefile to: PG_CPPFLAGS = -I$(ag_include_dir) -I$(ag_include_dir)/parser solved the problem for me -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] joefagan commented on issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
joefagan commented on issue #75: URL: https://github.com/apache/incubator-age/issues/75#issuecomment-862129183 Thank you for the tip. There is a plan to change the format of the documentation, which may alleviate the issue. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw commented on issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
seo-kw commented on issue #75: URL: https://github.com/apache/incubator-age/issues/75#issuecomment-862134886 > > > Thank you for the tip. > There is a plan to change the format of the documentation, which may alleviate the issue. Ohh. This is a little thing, But might helpful. Thanks for the attention! -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] seo-kw edited a comment on issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
seo-kw edited a comment on issue #75: URL: https://github.com/apache/incubator-age/issues/75#issuecomment-862134886 > > > Thank you for the tip. > There is a plan to change the format of the documentation, which may alleviate the issue. Ohh. Thanks for the attention! It might be helpful! -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] sstubbs commented on issue #54: Citus Compatibility
sstubbs commented on issue #54: URL: https://github.com/apache/incubator-age/issues/54#issuecomment-863485692 Is there anything I can test with this to help? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug commented on issue #85: project build problem( make -j option .., bison dependency )
emotionbug commented on issue #85: URL: https://github.com/apache/incubator-age/issues/85#issuecomment-863683416 @dehowef OK, I created PR. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] dehowef commented on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
dehowef commented on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-863562071 I put out a patch that corrects this -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] joefagan edited a comment on issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
joefagan edited a comment on issue #75: URL: https://github.com/apache/incubator-age/issues/75#issuecomment-863833349 Meanwhile, there's a firefox extension that I think stops that behaviour but I haven't tested it. https://addons.mozilla.org/en-US/firefox/addon/zerowidth-detection/ -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #66: Formatting create graph error on duplicate
JoshInnis commented on issue #66: URL: https://github.com/apache/incubator-age/issues/66#issuecomment-864156343 A patch was added to master that should alter the error message to "ERROR: graph "my_graph_name" already exists" It is scheduled to go into the next release to. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] dehowef edited a comment on issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
dehowef edited a comment on issue #79: URL: https://github.com/apache/incubator-age/issues/79#issuecomment-863562071 I pushed a commit that addresses this issue. Thanks for pointing it out. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] joefagan commented on issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
joefagan commented on issue #75: URL: https://github.com/apache/incubator-age/issues/75#issuecomment-863833349 There's a firefox extension that I think stops that behaviour but I haven't tested it. https://addons.mozilla.org/en-US/firefox/addon/zerowidth-detection/ -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] dehowef commented on issue #85: project build problem( make -j option .., bison dependency )
dehowef commented on issue #85: URL: https://github.com/apache/incubator-age/issues/85#issuecomment-863629857 @emotionbug I think your solution of adding options would be best. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] joefagan commented on issue #54: Citus Compatibility
joefagan commented on issue #54: URL: https://github.com/apache/incubator-age/issues/54#issuecomment-864155701 @sstubbs Perhaps you could try to load both Citus and AGE extension and see whether they can both load together? Is order important? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug closed issue #85: project build problem( make -j option .., bison dependency )
emotionbug closed issue #85: URL: https://github.com/apache/incubator-age/issues/85 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis closed issue #52: exists `label(...)` function in AGE?
JoshInnis closed issue #52: URL: https://github.com/apache/incubator-age/issues/52 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] dehowef closed issue #79: In assigning label type which is not same as you want to create, Database is forcibly terminated.
dehowef closed issue #79: URL: https://github.com/apache/incubator-age/issues/79 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] bitninejy commented on issue #67: PSQL recreates a graph that was already created with PG
bitninejy commented on issue #67: URL: https://github.com/apache/incubator-age/issues/67#issuecomment-864542225 @audiBookning I tried but I couldn't find this issues using psql. Can you show your Development settings? -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #23: Version 0.3.0 tag
JoshInnis commented on issue #23: URL: https://github.com/apache/incubator-age/issues/23#issuecomment-865165092 There is a release called 'v0.3.0.rc0-incubating' the naming conventions were altered for the first incubating Apache release. Version 0.4.0 resumes the v0.2 release naming conventions. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #23: Version 0.3.0 tag
JoshInnis commented on issue #23: URL: https://github.com/apache/incubator-age/issues/23#issuecomment-865165092 There is a release called 'v0.3.0.rc0-incubating' the naming conventions were altered for the first incubating Apache release. Version 0.4.0 resumes the v0.2 release naming conventions. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] LinuxJedi opened a new issue #88: Transaction cannot see own data?
LinuxJedi opened a new issue #88:
URL: https://github.com/apache/incubator-age/issues/88
I'm probably doing something wrong here, but for some reason I cannot get
data created in a transaction to be seen in the same transaction. It is only
seen after commit. For example:
```sql
cmdb=# begin;
BEGIN
cmdb=*# SELECT * FROM cypher('cmdb', $$ CREATE (a:Part {part_num: '678'})
$$) as (a agtype);
a
---
(0 rows)
cmdb=*# SELECT * FROM cypher('cmdb', $$ MATCH (a:Part {part_num: '678'})
RETURN a $$) as (a agtype);
a
---
(0 rows)
cmdb=*# commit;
COMMIT
cmdb=# SELECT * FROM cypher('cmdb', $$ MATCH (a:Part {part_num: '678'})
RETURN a $$) as (a agtype);
a
-
{"id": 844424930131973, "label": "Part", "properties": {"part_num":
"678"}}::vertex
(1 row)
```
Am I doing something wrong here or is this a bug?
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #88: Transaction cannot see own data?
JoshInnis commented on issue #88: URL: https://github.com/apache/incubator-age/issues/88#issuecomment-866244276 Hi, we will take a look at this -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis opened a new issue #89: Execution Phase node ExecMaterial does not rescan child nodes
JoshInnis opened a new issue #89:
URL: https://github.com/apache/incubator-age/issues/89
### Background
The ExecMaterial node in an Execution Tree may not rescan it's children
nodes. The material node acts as an intermediary between it's parent and it's
children. During the initial run, MaterialNode will execute its subplans, cache
the results in a data structure called a Tuplestorestate (postgres has only
exposed the name of, the structure is hidden in Tuplestorestate.c), and pass
the child tuple to its parent.
When the node is notified it will be rescanned or it will change scan
direction. The material node will try to get the needed tuple in its local
Tuplestorestate before scanning the child Append node. Assuming the above query
will return at least one result, the tuplestorestate will be used.
The following query will use a MaterialNode in it's execution:
`SELECT * FROM cypher('G', $$ match (a)-[e]->(b) delete e return e$$) AS (u
agtype);`
The Execution Tree:
```
SELECT * FROM cypher('G', $$EXPLAIN match ()-[e]->(b) delete e return e$$)
AS (u agtype);
QUERY PLAN
Custom Scan (Cypher Delete) (cost=0.00..0.00 rows=0 width=32)
-> Subquery Scan on _ (cost=0.00..3.06 rows=3 width=32)
-> Nested Loop (cost=0.00..3.03 rows=3 width=96)
Join Filter: (graphid_to_agtype(e.end_id) =
graphid_to_agtype(b.id))
-> Append (cost=0.00..1.03 rows=3 width=38)
-> Seq Scan on _ag_label_edge e (cost=0.00..0.00
rows=1 width=56)
-> Seq Scan on edge e_1 (cost=0.00..1.02 rows=2
width=29)
-> Materialize (cost=0.00..1.05 rows=3 width=8)
-> Append (cost=0.00..1.03 rows=3 width=8)
-> Seq Scan on _ag_label_vertex b
(cost=0.00..0.00 rows=1 width=8)
-> Seq Scan on vertex b_1 (cost=0.00..1.02
rows=2 width=8)
(11 rows)
```
Cypher's Delete clause (The Custom Scan node at the top of the execution
tree) attempts to dive into its children to get the physical tuple that it has
been asked to delete. Which is stored in the SeqScan, for the above query
(DELETE, CREATE, SET, or REMOVE may store it also). It needs this information
because we need the delete clause to mark the tuple as deleted*.
*Deleting a tuple in Postgres whether using Cypher's or Postgres' delete
functionality does't actually delete data, they just mark it as no longer a
valid tuple for future queries.
### Problem
The problem is that when the Materialize Node passes a cached tuple: the
SeqScan is not going to be holding the physical tuple anymore, NULL will be
returned to Cypher Delete node. The delete clause then cannot find the tuple
and doesn't delete the tuple.
### Solution
Instead of the DELETE (or SET/REMOVE) using its children to get the physical
location of the tuple on disc, the clause get it themselves. We start a new
scan on the table until we find the physical tuple. Use the id, which is unique
per edge/vertex in any given graph.
### Considerations
This will slow down performance, because we have to scan the disc for the
tuple's location ourselves. However, using the execution tree when possible and
scanning the tables when not will be time consuming and potentially
inconsequential relative to other performance solutions that could render this
dual retrieval solution useless.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #55: How to delete Edge?
JoshInnis commented on issue #55: URL: https://github.com/apache/incubator-age/issues/55#issuecomment-866387870 This issue is two things. The default behaviour when the RETURN clause is not specified is incorrect and it is related to the more general problem outlined here: https://github.com/apache/incubator-age/issues/89. The patch to fix this should be pushed shortly. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #89: Execution Phase node ExecMaterial does not rescan child nodes
JoshInnis commented on issue #89: URL: https://github.com/apache/incubator-age/issues/89#issuecomment-866394282 JIRA Ticket: https://issues.apache.org/jira/browse/AGE2-192 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis commented on issue #89: Execution Phase node ExecMaterial does not rescan child nodes
JoshInnis commented on issue #89: URL: https://github.com/apache/incubator-age/issues/89#issuecomment-867789158 A similar issue occurs with Hash Joins. They finish scanning it children, before its parent's run. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis closed issue #55: How to delete Edge?
JoshInnis closed issue #55: URL: https://github.com/apache/incubator-age/issues/55 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] JoshInnis closed issue #89: Execution Phase node ExecMaterial does not rescan child nodes
JoshInnis closed issue #89: URL: https://github.com/apache/incubator-age/issues/89 -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] Halkrine opened a new issue #91: Is possible to load extension automatically?
Halkrine opened a new issue #91: URL: https://github.com/apache/incubator-age/issues/91 Hi nice to meet you AGE. As a AGE beginner, I have a question, so submitted issue. When I run pgadmin, I have to load 'age' extension every time(AGE is installed by docker). So, is possible way to load age extension automatically? I can't found how to do.. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] emotionbug commented on issue #91: Is possible to load extension automatically?
emotionbug commented on issue #91: URL: https://github.com/apache/incubator-age/issues/91#issuecomment-868278492 edit `shared_preload_libraries` on `postgresql.conf` ( e.g., /var/lib/postgresql/data/postgresql.conf ) ``` # example shared_preload_libraries = 'age'# (change requires restart) ``` -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] Halkrine commented on issue #91: Is possible to load extension automatically?
Halkrine commented on issue #91: URL: https://github.com/apache/incubator-age/issues/91#issuecomment-868286632 > > > edit `shared_preload_libraries` on `postgresql.conf` ( e.g., /var/lib/postgresql/data/postgresql.conf ) > > ``` > # example > shared_preload_libraries = 'age'# (change requires restart) > ``` Thanks! I'll try it. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] eyab closed issue #75: I just got found Apache_AGE_Guide.pdf browser comparability problem in firefox.
eyab closed issue #75: URL: https://github.com/apache/incubator-age/issues/75 -- 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 unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] eyab closed issue #56: Case sensitivity for label names
eyab closed issue #56: URL: https://github.com/apache/incubator-age/issues/56 -- 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 unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] eyab closed issue #49: Please document a rust client
eyab closed issue #49: URL: https://github.com/apache/incubator-age/issues/49 -- 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 unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] eyab closed issue #29: main advantage of using AGE
eyab closed issue #29: URL: https://github.com/apache/incubator-age/issues/29 -- 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 unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] SofiaJorissen opened a new issue #92: Change the output of the Hello World sample to say "Hello there or stranger"
SofiaJorissen opened a new issue #92: URL: https://github.com/apache/incubator-age/issues/92 -- 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 unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-age] SofiaJorissen opened a new issue #93: Change the output of the Hello World sample to say "Hello there or stranger"
SofiaJorissen opened a new issue #93: URL: https://github.com/apache/incubator-age/issues/93 [](url) -- 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 unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
