Re: [orientdb] Transitive(?) index

Hi Alessandro - It's 2.1.2 Thanks Dmitri On Nov 2, 2015, at 3:36 AM, alessandrorot...@gmail.com wrote: > Hi, > which version of OrientDb are you using ? > > Kind regards, > Alessandro > > -- > > --- > You received this message because you are subscribed to a topic in the Google > Groups

[orientdb] javassist Nullpointer Exception in OObjectProxyMethodHandler

Hi guys, I tried to recompile a project today that used to work just fine, and I am getting the following exception: Caused by: java.lang.NullPointerException at com.orientechnologies.orient.object.enhancement.OObjectEntitySerializer. checkClassRegistration(OObjectEntitySerializer.java:350)

Re: [orientdb] Referential integrity

Luigi - Thanks a lot! The schema query is perfect. Dmitri On Nov 2, 2015, at 5:16 AM, Luigi Dell'Aquila wrote: > Hi Dmitri, > > if you have a full schema defined you can query it with > > select customFields from ( > select > expand(classes > ) from

[orientdb] Re: Transitive(?) index

Hi, when I try the following command "CREATE INDEX transidx ON myclass.prop1.prop2 NOTUNIQUE" I get an OCommandExecutionException: Class myclass.prop1.prop2 not found Alessandro -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe

[orientdb] Re: Upgraded to ODB 2.1.5 and now Studio delivers a 404.

I just downloaded and installed the Enterprise Edition and now Studio is working. That leads me to believe, something is wrong with Studio in the 2.1.5 Community Version. If anyone can confirm to Studio working fine for them (or not) I would be greatly appreciative. I opened an issue on Github

[orientdb] Re: Controlling edge multiplicity and direction in OrientDB, can it be improved?

I understand your point, but want to warn - if we are talking about graph database - understanfing, that edges are "first class citizens" - is essential. Working with relations directly, thinking of them as of real (not hidden) part of the system is what makes this concept so powerful. As in

[orientdb] Re: Controlling edge multiplicity and direction in OrientDB, can it be improved?

You see, that is the problem with me. ODB says, "Use the graph API, because then the graph relationships are handled automatically for you:" Well, that seems to be true, but only to a point. When you say I have to still think about relationships being stored in some list and that vertexes are

[orientdb] Re: Transitive(?) index

Hi, which version of OrientDb are you using ? Kind regards, Alessandro -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [orientdb] Cluster OrientDB in Kubernetes (AWS, GCE, Azure, etc.)

Hi Dean, Hazelcast people is taking care of this but ofc it will depend on a release and how fast OrientDB merges it. Ask Christoph Engelbert (https://twitter.com/noctarius2k) https://github.com/noctarius/hazelcast-kubernetes-discovery about it. Cheers, Pires On Sun, Nov 1, 2015 at 9:40 PM,

Re: [orientdb] Cluster OrientDB in Kubernetes (AWS, GCE, Azure, etc.)

Hi Paulo, We usually are pretty aligned to the last version of HZ, so if they release something we could embrace in "develop" version (now 2.2.0-SNAPSHOT). Best Regards, Luca Garulli Founder & CEO OrientDB On 2 November 2015 at 10:07, Paulo Pires

[orientdb] Re: Controlling edge multiplicity and direction in OrientDB, can it be improved?

If I want to map marriedTo, (for monogamous marriages), then I want a one2one relationship. No more, no less. Thinking about if I wanted "IsHusbandOf" and "IsWifeOf" edges, those would be unidirectional edges. Hmmthat scenario isn't covered in my suggestion. Maybe that was the "SIMPLE" in

Re: [orientdb] Referential integrity

Hi Dmitri, if you have a full schema defined you can query it with select customFields from ( select expand(classes) from metadata:schema ) where name="YourClassName" and select customFields from ( select expand(properties) from ( select expand(classes) from metadata:schema )