Hi,
To create graph db in such way just use
db = Orient.instance().getDatabaseFactory().createDatabase("graph", "plocal:"
+ dbPath)
if (!db.exists()) {
info("DB does not exist, BaasBox will create a new one");
db.create();
}
About the second question, you have several variants.
Two of them:
1. db.addVertex("class:" + CLASS_VERTEX_NAME);
2. db.addVertex(CLASS_VERTEX_NAME, null);
On Thu, Jan 30, 2014 at 5:30 PM, Claudio <[email protected]> wrote:
> Hi Luca,
> we use the old OGraphDatabase API to create a new fresh graph database if
> it does not exists when our application starts.
> db = new OGraphDatabase( "plocal:" + dbPath ) ;
> if (!db.exists()) {
> info("DB does not exist, BaasBox will create a new one");
> db.create();
> }
>
> As far I know the OrientGraph API hasn't got the exists() method, on the
> contrary, its constructor raises an error if the specified DB does not
> exists.
> Any advice on this?
>
> Furthermore we use it to create vertices:
> ODocument vertex = db.createVertex(CLASS_VERTEX_NAME);
>
> Inspecting the OrientGraph API, I cannot find a similar API. I just found
> the addVertex(iClassName, iClusterName) that accepts two parameters
> instead of just the class name
>
> Thanks,
> Claudio
>
>
> Il giorno mercoledì 29 gennaio 2014 11:26:21 UTC+1, Lvc@ ha scritto:
>
>> Hi all,
>> we're very close to merge the new storage structure to the 1.7 branch.
>> Andrey has some *awesome numbers *about the performance of the new
>> engine in terms of benchmarks, he will share them with us on this group
>> very soon.
>>
>> But in order to complete the merge, we should *remove the old Graph API:
>> OGraphDatabase*! This is mainly for 2 big reasons:
>>
>> 1. it's not compatible with *Lightweight* edges and other
>> improvements we introduced since version 1.4.x
>> 2. it heavily uses *MVRB-Tree indexes* so it wouldn't scale on the
>> new storage structure
>>
>> So after a while we deprecated the old Graph API, it's time to removed it
>> from the v1.7 code base. I know some users are still sticked with this API,
>> they can decide to:
>>
>> 1. Migrate to the Blueprints API (well documented on OrientDB &
>> TinkerPop sites)
>> 2. Stay with old API and remain sticked to last OrientDB v1.6.x.
>>
>> Obviously we strongly suggest 1st solution!
>>
>> For the users want to migrate we will provide a new guide to migrate the
>> old code (very easy, most of the concepts are the same). In this way they
>> could benefits of HUGE improvement with last version of OrientDB, specially
>> with big databases.
>>
>> Any comments are welcome :-)
>>
>> Lvc@
>>
>> --
>
> ---
> 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 [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Best regards,
Andrey Lomakin.
Orient Technologies
the Company behind OrientDB
--
---
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
