; RETURN DISTINCT driver.@rid AS DriverID, driver.name AS DriverName,
>>> car.cost AS CarCost
>>>
>>> Thanks
>>>
>>> Luigi
>>>
>>> Il giorno mer 6 mar 2019 alle ore 22:46 Michael Faughn <
>>> m.fa...@prometheu
SELECT * FROM (MATCH {Class: Person, as: driver, where:(name='Bob')}-Driving
->{Class: Vehicle, as:car} RETURN driver.@rid AS DriverID, driver.name AS
DriverName, car.cost AS CarCost)
results in the following:
DriverID
DriverName
CarCost
#332:0
)
>
> Thanks
>
> Luigi
>
>
> Il giorno mar 26 feb 2019 alle ore 17:01 Michael Faughn <
> m.fa...@prometheuscomputing.com > ha scritto:
>
>> Thanks Luigi. Creating an abstract class to represent an interface won't
>> work*. If you did this then
> them)
>
> I hope it helps
>
> Thanks
>
> Luigi
>
> Il giorno lun 25 feb 2019 alle ore 16:17 Michael Faughn <
> m.fa...@prometheuscomputing.com > ha scritto:
>
>> I'm having a go at implementing an OGM for Ruby. More precisely, an OGM
>> th
> different extensions on different products, so the migration still requires
> some effort.
>
> Thanks
>
> Luigi
>
> Il giorno gio 14 feb 2019 alle ore 23:31 Michael Faughn <
> m.fa...@prometheuscomputing.com > ha scritto:
>
>> I'm trying to determine the feasibili
I'm trying to determine the feasibility of switching to a graph database
for my company's toolchain. I've already mostly settled on OrientDB as the
most likely candidate. We would likely be looking at writing a Ruby OGM
for OrientDB if we do move forward*. I'm looking for an analysis of the
