Hi Jenica,
I'm stuck with the same problem. I run a javascript server-side function
with db.command('sql','create vertex v') and I can't come up with a way to
get the rid of that vertex. Have you found a way?
cheers
sábado, 25 de Julho de 2015 às 06:24:53 UTC+1, Jenica escreveu:
I am new
HI,
it's not very clear, you would create a scheme like this:
https://lh3.googleusercontent.com/-iVGcKvM1vAY/VbY5JeLOdSI/AEk/cVEQ5c7w13Q/s1600/ereditarriet%25C3%25A0.jpg
then extract the RID of the superclass Person to create the edge between the
person class and
Yes, but I'm trying to move away from using properties because they may not
be unique. There might be multiple John Smith born on the same date. Since
each created vertex has its own RID number I was thinking of using those
values instead to link the superclass to the subclass. I know this can be
There is still no need to make the name etc. separate vertices rather than
properties.
You want each John Smith to have a unique rid. Just make the name fields
and date of birth fields properties of class Person. Then each new Person
will automatically have a unique rid
You gain
Hi,
I was hoping breaking up the data would help reduce the end size of the
database and even making it more efficient.
If that's not the case, I'll keep them as properties.
thank you for your help
Jenica
On Mon, Jul 27, 2015 at 12:13 PM, normanLinux thenh...@gmail.com wrote:
There is still
Unfortunately, you would be more likely to *increase *the size of your
database. A vertex will require a certain minimum storage space. The
properties would not add much to this, but if each property were a separate
vertex each would take that minimum.
On Monday, 27 July 2015 22:09:26 UTC+1,
