Christian Himpe

icon indicating a website link https://himpe.science

icon company University of Münster icon location Sol, Orion Arm icon location Research data engineering at @ulbmuenster

Results 151 comments of Christian Himpe

What are the permitted ways to make prepared statement queries or inserts? Ie. To avoid SQL injection? Is it just JDBC? Postgres?

The HTTP API can pass parameters into [queries](https://docs.arcadedb.com/#HTTP-ExecuteQuery) and [commands](https://docs.arcadedb.com/#HTTP-ExecuteCommand). Also, the [Java API](https://docs.arcadedb.com/#_java-reference) allows passing parameters. I guess, in both cases these parameterized queries can easily be encapsulated into...

What are the permitted ways to make prepared statement queries or inserts? Ie. To avoid SQL injection? Is it just JDBC? Postgres?

I don't think I can solve your problem(s), but here are some remarks that may hopefully help: * Above, I meant, for example, using a function to wrap the statement...

What are the permitted ways to make prepared statement queries or inserts? Ie. To avoid SQL injection? Is it just JDBC? Postgres?

To my understanding this is not how parameters work, at least in ArcadeDB. A parameter is placed into the parameterized query or command as its type. For example `SELECT FROM...

What are the permitted ways to make prepared statement queries or inserts? Ie. To avoid SQL injection? Is it just JDBC? Postgres?

If this is a response to me: sorry, I was referring to the HTTP API here.

SQL: Out-of-memory when `CREATE EDGE ... IF NOT EXISTS` for existing edges with array of destination vertices

Some more details and a more reduced test case: * This happens only if the source `FROM ... ` **or** the target `TO ...` is an array of more than...

SQL: Out-of-memory when `CREATE EDGE ... IF NOT EXISTS` for existing edges with array of destination vertices

@robfrank I am testing the latest head with the fix. The OOM is gone, but it seems the `IF NOT EXISTS` is somewhat ignored. For example the following commands keep...

SQL: Out-of-memory when `CREATE EDGE ... IF NOT EXISTS` for existing edges with array of destination vertices

I will test again, but in the graph view it looked like each `CREATE EDGE` creates **new** edges, which should not happen for `IF NOT EXISTS`, if I am not...

SQL: Out-of-memory when `CREATE EDGE ... IF NOT EXISTS` for existing edges with array of destination vertices

Yes. I tested the changes manually in studio with the example above. Everytime I call `CREATE EDGE ... IF NOT EXISTS` it seems new edges are created as new edges...

SQL: Out-of-memory when `CREATE EDGE ... IF NOT EXISTS` for existing edges with array of destination vertices

IMHO the problem is not what is getting returned, but what is created: There should not be any new edges created if edges between the vertices already exists. Sorry if...

SQL: Out-of-memory when `CREATE EDGE ... IF NOT EXISTS` for existing edges with array of destination vertices

@robfrank The latest changes fixed the problem. Great! Thanks