OrientDB

gremlin filter on Hashmap property without using a lambda

由 痴心易碎 提交于 2021-01-28 18:54:11
问题 If I have a vertex in a graph database where one of the properties is a map, is there a way to filter on properties of the map without using a lambda? Create the vertex like this: gremlin> v = graph.addVertex(label, 'LABEL') ==>v[68] gremlin> g.V(68).property('prop', [ key: 'val' ]) ==>v[68] gremlin> g.V(68).valueMap() ==>{prop=[{key=val}]} Is there a way to filter for vertices by prop.key == 'val' without using a lambda? gremlin> g.V().filter{ it.get().values('prop').next().get('key') ==

OrientDB: How to flatten nested heirarchy into a single record

由 瘦欲@ 提交于 2021-01-28 12:10:40
问题 I have a structure that looks something like this: How can I traverse my Page and get back a flat record so that each row represents all of data from the root node and its edges. My use case is that I'm producing a csv file. so from the example above, i would like to create a row for each post. Each record should contain all fields from post, the language name, the page name, and the network name. From what I can tell, when you do any kind of traversal, it only gives you the result of the

How to structure a graph database to support 3-way relationships?

由 我怕爱的太早我们不能终老 提交于 2020-12-04 03:44:27
问题 I've been trying to figure out a database backend for a personal webapp I've been working on. Due to the flexibility that I require in the data, a relational database isn't feasible and some form of document storage is likely. When I learned about graph databases, I felt that this would be perfect. However, I've run into someone of an issue: I need to be able to define a 3-way relationship in some way. I haven't decided on a database yet, but I've been tinkering with Neo4j, so I'll use Cypher

How to structure a graph database to support 3-way relationships?

由 ぃ、小莉子 提交于 2020-12-04 03:41:29
问题 I've been trying to figure out a database backend for a personal webapp I've been working on. Due to the flexibility that I require in the data, a relational database isn't feasible and some form of document storage is likely. When I learned about graph databases, I felt that this would be perfect. However, I've run into someone of an issue: I need to be able to define a 3-way relationship in some way. I haven't decided on a database yet, but I've been tinkering with Neo4j, so I'll use Cypher

Creating Edges with OrientDB-NET.binary in a transaction

由 不打扰是莪最后的温柔 提交于 2020-06-01 01:50:28
问题 I am trying to use OrientDB-NET.binary, extending it to improve ease-of-use among my development team. I am trying to create syntax which is similar to dapper, as that's what we're using for our MSSQL and MySQL connections. This should make it easier on our development team swapping between the two technologies. I'd also like my extensions to function with transactions. Here's my Insert extension as it is now: public static void Insert<T>(this ODatabase db, T model, OTransaction transaction)

Nexus3.19版本密码重置

由 时光总嘲笑我的痴心妄想 提交于 2020-03-18 13:31:47
参考地址： https://support.sonatype.com/hc/en-us/articles/213467158-How-to-reset-a-forgotten-admin-password-in-Nexus-3-x 1.停止服务 # ./nexus stop Shutting down nexus 2.进入OrientDB控制台（OrientDB是不一开源NoSql数据库） #cd ../nexus-3.19.1-01/lib/support # ls nexus-orient-console.jar 加载jar包 #java -jar ./lib/support/nexus-orient-console.jar 提示错误：Exception in thread "main" java.lang.UnsupportedClassVersionError: org/sonatype/nexus/orient/console/Main : **Unsupported major.minor version 52.0** 查看JAVA版本是否过低 # java -version java version "1.7.0_80" Java(TM) SE Runtime Environment (build 1.7.0_80-b15) Java HotSpot(TM) 64

Infinite recursion when serializing OrientDB RecordID

由 有些话、适合烂在心里 提交于 2020-02-02 10:21:16
问题 In my schema I have an abstract class like this: @JsonAutoDetect(JsonMethod.NONE) public abstract class AbstractEntity { @Id private Object id; @Version private Integer version; public AbstractEntity() {} @JsonProperty // this annotation causes infinite recursion public Object getId() { return id; } } This class is used as superclass for every entity, for example: @JsonAutoDetect(JsonMethod.NONE) public class Usuario extends AbstractEntity { private Cadastro cadastro; protected Usuario() {}

How do I create an auto-incrementing index/a sequence for an OrientDB database using the Java Document API?

由 爷，独闯天下 提交于 2020-01-23 12:07:21
问题 I am using OrientDB with Java via its Document API. I have a simple Class called items which has an attribute ID . I explicitly declare the schema like this: OSchema schema = db.getMetadata().getSchema(); OClass itemsClass = schema.createClass("items"); itemsClass.createProperty("ID", OType.LONG); and then create an index on ID : CREATE INDEX items.ID ON items (ID) UNIQUE . Now when I create a new item (something like ODocument doc = new ODocument("items") etc.), I would like the ID for the

orientDB cant delete value from map

由 耗尽温柔 提交于 2020-01-17 06:17:43
问题 I been trying the following query: UPDATE #15:1 REMOVE jsonData.contactName And receive the following { "result": [ { "@type": "d", "@version": 0, "value": 1 } ], "notification": "Query executed in 0.027 sec. Returned 1 record(s)" } Which mean been succedd, Now when i query to check the value i get: select * from #15:1 { "result": [ { "@type": "d", "@rid": "#15:1", "@version": 6, "@class": "TestClass", "postUrl": "ABC", "postCategory": "#11:497", "jsonData": { "contactName": "JHON" }, "
订阅 OrientDB