[I] Unable to drop column from vlabel tables [age]

2024-03-04 Thread via GitHub


mingfang opened a new issue, #1639:
URL: https://github.com/apache/age/issues/1639

   If I add a new column to a vlabel table, then I will not be able to drop 
that column.
   Here are the steps to reproduce
   ```sql
   -- create test graph and table
   SELECT * FROM ag_catalog.create_graph('drop_column');
   SELECT ag_catalog.create_vlabel('drop_column', 'table1');
   
   -- add new column
   ALTER TABLE drop_column.table1 ADD COLUMN col1 TEXT;
   
   -- fail to drop with error: ERROR:  table "table1" is for label "table1"
   ALTER TABLE drop_column.table1 DROP COLUMN col1;
   ```
   
   It's almost as if AGE thinks I'm trying to drop the entire table and not 
just a column.
   


-- 
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.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] AGEViewer or browser is not clickable..and i have attched the error from console below..can anyone help me out [age-viewer]

2024-03-04 Thread via GitHub


HackettJP commented on issue #162:
URL: https://github.com/apache/age-viewer/issues/162#issuecomment-1977903883

   My fix works, which is fix the errors in the code and the Security IFrame 
injection  is not created, go though each of the red errors line listed at 
compile that says error  and add unique aria-label ="aria1" etc and 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.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[I] GraphQL Driver for Apache AGE [age]

2024-03-04 Thread via GitHub


aked21 opened a new issue, #1638:
URL: https://github.com/apache/age/issues/1638

   **Describe the solution you'd like**
   A GraphQL driver will allow GraphQL users or applications to access Apache 
AGE (on PostgreSQL) using GraphQL queries.

   **Describe alternatives you've considered**
   Hasura and PostGraphile
   


-- 
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.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Setting all properties with map object causes error [age]

2024-03-04 Thread via GitHub


mingfang commented on issue #1634:
URL: https://github.com/apache/age/issues/1634#issuecomment-1977738460

   wow that was fast. thanks!


-- 
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



Re: [I] Setting all properties with map object causes error [age]

2024-03-04 Thread via GitHub


jrgemignani commented on issue #1634:
URL: https://github.com/apache/age/issues/1634#issuecomment-1977719509

   @mingfang PR #1637 created to fix this in the master branch.


-- 
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



Re: [I] Setting all properties with map object causes error [age]

2024-03-04 Thread via GitHub


jrgemignani commented on issue #1634:
URL: https://github.com/apache/age/issues/1634#issuecomment-1977605983

   @mingfang Will look into 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.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] MERGE using array not working in some cases [age]

2024-03-04 Thread via GitHub


jrgemignani commented on issue #1630:
URL: https://github.com/apache/age/issues/1630#issuecomment-1977491224

   PR #1636 created to fix this issue in the master branch.


-- 
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



Re: [I] MERGE using array not working in some cases [age]

2024-03-04 Thread via GitHub


mingfang commented on issue #1630:
URL: https://github.com/apache/age/issues/1630#issuecomment-1977373778

   @jrgemignani 
   Amazing detective work! 
   Thanks for figuring it out so quickly.


-- 
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



Re: [I] MERGE using array not working in some cases [age]

2024-03-04 Thread via GitHub


jrgemignani commented on issue #1630:
URL: https://github.com/apache/age/issues/1630#issuecomment-1977315056

   @mingfang I should have a PR for the fix today. This particular bug is due 
to PG function `remove_unused_subquery_outputs`. For whatever reason, the PG 
logic feels that it is okay to remove the variable by replacing it, in place, 
with a NULL constant. The fix involves wrapping the variable with a volatile 
function so that it is kept.


-- 
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



Re: [I] Need postgres with graph extensions running on windows OS [age]

2024-03-04 Thread via GitHub


MironAtHome commented on issue #1542:
URL: https://github.com/apache/age/issues/1542#issuecomment-1977025250

   Hello, I really appreciate effort.
   My fork just got all the changes needed for the code.
   There is still a bit of work left to document steps needed to setup windows 
flavor of flex, add build targets for the Visual Studio project file and wrap 
up on drawing table based ingestion, regression and cleanup.
   Please do let me know if I can be of any assistance, I am hoping to wrap up 
work on my fork by end of this week.
   Thank you greatly for your 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.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] OPTIONAL MATCH should act as outer relationship, acts as cross join [age]

2024-03-04 Thread via GitHub


MironAtHome commented on issue #1629:
URL: https://github.com/apache/age/issues/1629#issuecomment-1977018339

   I think it is not really question of match, but a question of what 
"optional" means.
   Based on what I have gathered from the documentation ( provided in the 
comments ) optional indicates outer kind of relationship.
   Which means that in case of an empty set(s) on one of the sides, it is 
treated as an null, whilst the other one, depending on the operator, suppose to 
either furnish an matching row, or no row.
   So, if one is to read it with an eye to standard sql, this falls into the 
case of full outer join.
   It would be very nice if there is a chance to clarify similar against some 
alternate engine?
   I didn't treat it with high severity, since performing hierarchical match, 
where 1st level is required and 2nd level is optional, query works correctly. 
So, we can do left outer join right now, and that gives us a chance with, 
perhaps one additional query step, satisfy need to perform outer join.
   However, if query could pick up proper outer join behavior, it would be 
helpful, particularly for some of the corner cases used to test data quality.
   Hope this clarification helps.


-- 
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