Forewarning, my questions might be a bit elementary, I'm new to orientdb.
So the cons with embedded would be that the relationship would only exist
in the owner and would be lost if the owner is deleted resulting in
ownerless objects and the owner objects would be larger?
The Pro would be more
I think I misunderstood what a linkset was. Now I see its a collection of
links. thanks
On Wed, Apr 8, 2015 at 8:20 PM, Jeffrey Auguste mrjaugu...@gmail.com
wrote:
I'm seeing the same error running select out() from vector1.
the configuration is vector1(linkbag) from edge1(linkset) to
vector2
I'm seeing the same error running select out() from vector1.
the configuration is vector1(linkbag) from edge1(linkset) to
vector2(linkbag).
It works fine with vector1(linkbag) from edge1(link) to vector2(linkbag).
Version 2.05
On Saturday, September 3, 2011 at 4:28:49 AM UTC-4, Lvc@ wrote:
OrientDB Server v2.0.2
To reproduce, load a csv with null values into a vector in strictmode with
all parameters set to mandatory.
On Friday, March 27, 2015 at 9:08:46 PM UTC-4, Jeffrey Auguste wrote:
My database is in strictmode and I have set all the field properties to
mandatory
My database is in strictmode and I have set all the field properties to
mandatory and remain nullable. Trying to load a csv into the vertex and it
fails when loading a null value.
Error: The field 'Vertex.Field' is mandatory, but not found on record:
The CSV record has a value of NULL for
My understanding so far is that OrientDB has two type of Edges. Regular and
Lightweight. The regular provides more flexibility and functionality at the
cost of additional storage and performance. Its also my understanding that
the lightweight edge is by default turned off with orientdb which
it?
On Thursday, March 12, 2015 at 11:39:04 AM UTC-4, Jeffrey Auguste wrote:
My understanding so far is that OrientDB has two type of Edges. Regular
and Lightweight. The regular provides more flexibility and functionality at
the cost of additional storage and performance. Its also my understanding
2015-03-12 16:32 GMT+01:00 Jeffrey Auguste mrjau...@gmail.com
javascript::
My understanding so far is that OrientDB has two type of Edges. Regular
and Lightweight. The regular provides more flexibility and functionality at
the cost of additional storage and performance. Its also my
lightweight edges on in any moment.
Actually to create a regular edge (instead of lightweight), defining a
class for it is not enough, you just have to explicitly add a property to
that.
Luigi
2015-03-12 17:55 GMT+01:00 Jeffrey Auguste mrjaugu...@gmail.com:
So it seems that both can coexist
