Hi Gav,
I will check this
On Thursday, October 30, 2014 7:14:43 AM UTC+2, Gav wrote:
>
> Hi,
>
> I've tried searching around but can't seem to find anyone else having this
> issue so thought I'd ask here.
>
> I've just started working with OrientDB and am loving it so far but can't
> seem to co
Hi,
Thanks for responding, I'm wondering if it's something on my machine as
I've gone for the simplest test case I can and I can't connect still. I
have a console app, the entire code is below:
static void Main(string[] args)
{
OClient.CreateDatabasePool(
"127.
Hi Nathan,
Why don't use OrientDB export/import?
Lvc@
On 5 November 2014 22:42, Nathan Frund wrote:
> Hi Lvc@,
>
> Originally, my source was from OrientDB itself. I've got a graph
> playground set up for exploration and testing with schema classes, etc.
> That's what I exported. After .saveGra
Hi Lvc@,
Originally, my source was from OrientDB itself. I've got a graph playground
set up for exploration and testing with schema classes, etc. That's what I
exported. After .saveGraphSON(), I tried splicing labels into the file by
hand, but after loading the file back in via .loadGraphSON(),
Is partial matching using LIKE supported on EMBEDDEDLIST types?
--
---
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 orient-database+unsubscr...@googlegroups.com.
Hi Nathan,
OrientDB 2.0-SNAPSHOT is able to do it when you import from Neo4j
preserving types as labels. What's your source?
Lvc@
On 5 November 2014 21:54, Nathan Frund wrote:
> Using: OrientDB 2.0-M2
>
> Is there a way to preserve vertex classes when exporting/importing
> GraphSON?
>
> Here's
Hi Ioannis,
What are you using for Profiling?
Did you measure it with validation disabled?
Can you try setting Massive Insert intent before the insert?
db.declareIntent( new OMassiveInsertIntent() );
Lvc@
On 5 November 2014 22:20, Ioannis wrote:
> VERSION 2.0-M2 - (September, 29th 2014)
> C
VERSION 2.0-M2 - (September, 29th 2014)
Cannot find the build.number file? :(
I am using Orient DB to enter timeseries data, as
per https://github.com/orientechnologies/orientdb/wiki/Time-series-use-case
To create the link structure (year->month->day->hour->) I create ODocuments
and set their f
Using: OrientDB 2.0-M2
Is there a way to preserve vertex classes when exporting/importing GraphSON?
Here's my (Groovy) server-side code for export:
g = orient.getGraphNoTx();
g.saveGraphSON ('/Users/Nathan/graph.json');
And for import:
g = orient.getGraphNoTx();
g.loadGraphSON ('/Users/Nathan
Yeah that was easy, thanks Luca.
Am Mittwoch, 5. November 2014 20:29:09 UTC+1 schrieb Lvc@:
>
> Hi Curtis,
> Sure:
>
> ALTER CLASS Person SUPERCLASS V
>
> Lvc@
>
>
>
> On 5 November 2014 20:24, 'Curtis Mosters' via OrientDB <
> orient-...@googlegroups.com > wrote:
>
>> Is there a way to change or
Hi Curtis,
Sure:
ALTER CLASS Person SUPERCLASS V
Lvc@
On 5 November 2014 20:24, 'Curtis Mosters' via OrientDB <
orient-database@googlegroups.com> wrote:
> Is there a way to change or even add a Superclass to a Class in the Studio?
>
> Or is it possible with a query?
>
> --
>
> ---
> You recei
Is there a way to change or even add a Superclass to a Class in the Studio?
Or is it possible with a query?
--
---
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 or
I think you can disable the standard constrains of Blueprints using
graph.setStandardElementConstraints(false);
Enrico
2014-11-05 16:23 GMT+01:00 Keith Freeman <8fo...@gmail.com>:
> I don't think there's a way to allow null values, but consider that you
> don't need to store nulls because queri
I don't think there's a way to allow null values, but consider that you
don't need to store nulls because queries like "select * from widgets where
prop1 is null" will return all widgets that don't have a "prop1" property.
This is a nice advantage of orient over relational databases.
On Wednes
Now that you mention it, I don’t think sails-orientdb likes:
“database: 'bGsn’”,
it prefers:
database: {
name: 'aGsn'
}
I remember changing it on my personal fork to enable support for both
formats.
Cheers
On Tuesday, 4 November 2014 22:25:35 UTC, Paolo Di Pietro wrote:
>
> Hi D
thank you :)
On Wednesday, 5 November 2014 09:56:11 UTC, Riccardo Tasso wrote:
>
> Wow, this is a hidden feature I've never heard of!
> It seems cool!
>
> The order of edges is insertion order or can be somehow tuned (by edge
> label, out/in vertex properties)?
>
> 2014-11-05 10:51 GMT+01:00 Luig
Hi Luca,
Thanks for your suggestion.
I would have added a bidirectional link, however in my query I have a WHERE
clause that limits Steps (it's a 1:1 relationship).
If I understand your suggestion correctly, I would select all the Schedules
and at the same time retrieve the associated Steps, ri
Hi Markus,
if you had bidirectional links between Schedule and WorkOrderWorkStep (If
you use the Graph model this is automatically managed), then you could do:
SELECT steps from Schedule ORDER BY startDateBackward
This would use the index. If you use the Graph model everything is easier:
SELECT
Good afternoon,
I'm trying to save a vertex that contains null values in some of their
properties and I'm receiving the following exception:
*Exception in thread "main" java.lang.IllegalArgumentException: Property
value can not be null*
* at
com.tinkerpop.blueprints.util.ExceptionFactory.prop
Hi Luca,
the "b" field is a LINK from class A to class B.
My real query looks like this: SELECT * from WorkOrderWorkStep ORDER BY
schedule.startDateBackward
Thus class WorkOrderWorkStep (A in my example) has a LINK via the field
"schedule" to class Schedule (B in my example).
EXPLAIN returns:
Hi,
I don't think this query will ever use indexes:
SELECT attribute1, attribute2 FROM A WHERE attribute1='something' AND
attribute2='somethingelse' ORDER BY b.date
Because the field is b.date. Try with explain:
EXPLAIN SELECT attribute1, attribute2 FROM A WHERE attribute1='something'
AND attrib
Thanks for the reply.
Is there a possibility to structure the SQL differently in order to make
the query faster?
On Wednesday, 5 November 2014 12:37:26 UTC+1, Curtis Mosters wrote:
>
> I'm also using ORDER BY in my LUCENE searches. And compared to Neo4j it is
> always slower. So I don't think y
I'm also using ORDER BY in my LUCENE searches. And compared to Neo4j it is
always slower. So I don't think you can do anything about this except
waiting for improvements on the ORDER BY like me ;)
Am Mittwoch, 5. November 2014 12:17:40 UTC+1 schrieb Markus Menner:
>
> Hi Ricardo,
>
> Sure, I've
Hi Ricardo,
Sure, I've created an index on B.date.
My query looks like this:
SELECT attribute1, attribute2 FROM A WHERE attribute1='something' AND
attribute2='somethingelse' ORDER BY b.date
Any idea how to speed this up?
I tested this with A having only 16K instances (no WHERE clause in this
Wow, this is a hidden feature I've never heard of!
It seems cool!
The order of edges is insertion order or can be somehow tuned (by edge
label, out/in vertex properties)?
2014-11-05 10:51 GMT+01:00 Luigi Dell'Aquila :
> Hi Stefan,
>
> I think this can help you
>
>
> http://www.orientechnologies.
Hi guys,
We postponed final 2.0 of a couple of weeks to make it more stable (many
issues raised in the last days).
Lvc@
On 5 November 2014 09:08, 'Curtis Mosters' via OrientDB <
orient-database@googlegroups.com> wrote:
> Well I think there are just coming bug fixes. And the date, well as far as
Hi Stefan,
I think this can help you
http://www.orientechnologies.com/docs/last/orientdb.wiki/Graph-Database-Tinkerpop.html#ordered-edges
Luigi
2014-11-05 10:35 GMT+01:00 :
> bump ... again
>
>
> On Tuesday, 4 November 2014 08:10:37 UTC, ste...@activitystream.com wrote:
>>
>>
>> And on more.
bump ... again
On Tuesday, 4 November 2014 08:10:37 UTC, ste...@activitystream.com wrote:
>
>
> And on more.
>
> I can fetch my Vertex easily using the Java API, I can traverse to
> adjacent vertices, via edges, and do most any thing.
> But if I want to avoid iterating through thousands of edges
Well the getVertices is using the Index for sure.
I use
for (Vertex title : txGraph.getVertices("Appln.ID", splitted[0])) {
title.setProperty("title", splitted[1]);
}
and going all over the ID index.
Am Mittwoch, 5. November 2014 00:36:55 UTC+1 schrieb hihim...@gmail.com:
>
> Hello :)
>
>
Well I think there are just coming bug fixes. And the date, well as far as
I know the final release was planned a month ago. I think there are just
too many small issues.
It's done when it's done ;) Or maybe tell us what you plan to do in case
the developers know if there might come any changes
30 matches
Mail list logo
