Re: [orientdb] Referential integrity

Hi Dmitri, Document layer does not manage link consistency, just for a matter of performance, but Graph layer does (eg. it removes dangling edges when you delete a vertex). My advice is to use edges instead of links, it will also give you another advantage, that is having bi-directional traversal

Re: [orientdb] Class physical name versus logical name?

Hi Harish, Using the short name in your use case seems to be a perfect fit. This way you will avoid all the consequences of changing class name, especially with cluster and index names. About property names, unfortunately there is no support for aliases right now. Even worse, if you do an ALTER

[orientdb] Transitive(?) index

Hello, The basic CREATE INDEX statement is: CREATE INDEX [ON (prop-names)] e.g. CREATE INDEX simpleidx myclass.prop1 NOTUNIQUE Now let's imagine that prop1 is a property which is a LINK to another class, which has a STRING property prop2 . Can I create a transitive(? if this is the

Re: [orientdb] com.orientechnologies.orient.core.exception.OConcurrentModificationException at Distributed mode

Hi Alexander, I suggest you to manage transaction retry anyway, here is an example http://orientdb.com/docs/last/Java-Multi-Threading.html#graph-api Thanks Luigi 2015-10-28 16:47 GMT+01:00 alexander anguiano : > I just ran into this problem. In your response you say

[orientdb] Re: [Announcement] Released OrientDB v2.1.5

I would imagine that a major bug with FULLTEXT LUCENE INDEX would be a blocking bug. The Issue 5184 bug makes any lucene index with more than one field useless. Did this just slip through the cracks or are people not really using

Re: [orientdb] Class physical name versus logical name?

Hi Scott, there is no practical limitation to the number of properties you can have in a class, you just have to consider that a single document cannot be bigger than 2GB and the schema is kept in a similar structure. There is no direct link from data to metadata (eg. from a record to its class)

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

Thanks for the input Ziink A. Though, you completely lost me with your example. I can't deny that ODB's approach might be more versatile. However, how controlling multiplicity should be a lot more straightforward and I just don't see how it works with the available commands? Let me give it a

[orientdb] Ostico Phporient driver timezone error

HI, In database inserted record Asia/kolkata timezone but using ostico phporient driver retrieve record from database timezone will be differ. how can i fix it. Regards, jayaraj -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To

Re: [orientdb] Class physical name versus logical name?

We're looking at doing something similar in our application. For all the attributes (even including the names of classes), we are looking to have API names and a field names. The API name will need to follow a given structure and can follow the field name. For instance, if the field name is

[orientdb] Re: [Announcement] Released OrientDB v2.1.5

Thanks On Friday, October 30, 2015 at 3:33:09 AM UTC+1, l.garulli wrote: > > Hi guys, > > We just released OrientDB v2.1.5. Please upgrade your production > environment with 2.1.x. > > For more information about the release: > https://github.com/orientechnologies/orientdb/releases/tag/2.1.5. >

Re: [orientdb] Referential integrity

Luigi - Thank you. I understand the tradeoff. OK, I have to manage this manually. What is the best way? Is there any way to query the schema and find out which objects have fields that reference a particular class? (so that I can NULL them and then remove the class) Regarding using Graph