Hi Adam,
Thank you very much, I just fixed the docs, the patch will be in the
official docs in a few minutes
Thanks
Luigi
2017-09-11 6:34 GMT+02:00 Oleksandr Gubchenko :
> You can edit the docs, thanks!
>
>
> Il giorno domenica 10 settembre 2017 20:58:23 UTC+2,
I
> open an issue on GitHub per each error?
>
> -Adam
>
> On Monday, September 4, 2017 at 8:56:59 AM UTC-4, Luigi Dell'Aquila wrote:
>>
>> Hi Adam,
>>
>> Thank you very much for reporting, I just fixed the docs, the new version
>> should be available i
Hi Adam,
Thank you very much for reporting, I just fixed the docs, the new version
should be available in a few minutes
Thanks
Luigi
2017-09-02 23:42 GMT+02:00 :
> I think this can be fixed by just replacing OSQLQuery with OSQLSynchQuery
>
> -Adam
>
> On Saturday,
Hi Xavier,
you can just do
DELETE FROM OFunction WHERE name = ...
Thanks
Luigi
2017-08-09 11:03 GMT+02:00 Xavier Rigal :
> Hi,
>
> I just created a function
>
> CREATE FUNCTION fixImage "return value.replace(new RegExp(\"src='/foo/\",
> 'g'), \"src='/images\");"
Hi Cristian,
Point 2 is already implemented in develop branch.
About point 3, if you mean having a streamed result-set from the queries,
it's already available in develop branch. About data streaming for BLOBs,
there are some low level APIs for this, but I'm afraid they don't work in
remote and I
Hi,
Unfortunately the answer for both questions is NO. Links are
unidirectional, so finding records that link to a specific record is a very
expensive operation, this is why OrientDB does not provide support for this.
If you want automatic link management, I suggest you to use edges instead.
Sorry, the first query is
TRAVERSE in('scopedEdge') FROM (
SELECT expand(in('scopeEdge'))
FROM V WHERE file IS NOT NULL
)
2017-06-19 15:26 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi Erik,
>
> I'm afraid I don't completely understand your model:
> -
Hi Erik,
I'm afraid I don't completely understand your model:
- how are the edges directed? From parent to child or from child to parent?
- are File and Folder two different classes that extend V?
- what does the "file" property represent? Is it a string or what?
If I got it right, you have
Hi John,
Yes, you can use OrientDB in-memory only specifying "memory:dbname" as the
connection URL.
Thanks
Luigi
2017-06-19 10:17 GMT+02:00 John :
>
> Hello, I'm not familiarized with the mode Ram Only
> 1) Do Orientdb use a mode Ram only?
> 2) If 1) is yes, who can
Hi Nicolas,
I'm pretty sure that I fixed this issue in a recent release, could you
please try with v 2.2.21?
Thanks
Luigi
2017-06-14 16:38 GMT+02:00 nicolas treiber <nicolas.trei...@gmail.com>:
> Hi Luigi. I use the 2.2.17
>
> Le mercredi 14 juin 2017 16:35:54 UTC+2, Luigi Dell
Hi Nicolas,
Which version of OrientDB are you using?
Thanks
Luigi
2017-06-14 16:08 GMT+02:00 nicolas treiber :
> Hi,
> I have a weird problem with Match queries with a WHILE.
> I have two classes: Gallery and Folder. Galleries and Folders can have
> multiples
Hi Pugazharasan,
v 2.0 is no longer supported, unfortunately in that version you cannot
execute filtering with < > between square brackets
Thanks
Luigi
2017-06-05 14:22 GMT+02:00 Pugazharasan Thirumalai
:
> Studio version : 2.0
>>
>> OrientDB version : 2.0.18
>>
>>
Hi,
Which version of OrientDB are you using?
We recently fixed some parsing issues in square brackets
Thanks
Luigi
2017-06-05 13:48 GMT+02:00 Ivan Mainetti :
> HAI,
> you can't use < > in square parenthesis conditions.
>
>
> Il giorno lunedì 5 giugno 2017 12:59:37
Hi,
There is no specific syntax to retrieve last records of a query without an
ORDER BY, but you can define an index on PROPERTY1, this will speed up the
sorting. Just consider that you cannot use two different indexes, one for
filtering and one for sorting, so you have to choose.
I hope it
Hi Ram,
The problem here is that the inner query (the TRAVERSE) can return a big
quantity of record. For each one of these records, the outer query has to
invoke the other sub-queries to calculate the LET variable assignments.
The first query can just fetch the first 11 records from the TRAVERSE,
Hi Marc,
The back-end of the graph visualization starts from vertices and then tries
to return all the edges that connect these vertices, regardless of the
original query.
I agree with you that it in some cases (like yours) it is not the expected
behavior, probably it can be enhanced. Could you
Hi John,
How are you doing the import? Are you working in transaction? Some code
will help us understand where the problem is
Thanks
Luigi
2017-05-05 3:53 GMT+02:00 John J. Szucs :
> Hello, OrientDB community! It's me again with another question.
>
> I am still
About the black magic, I think the query planner is trying to process is
from right to left, but when it finds a parenthesis block it fails to
traverse it backwards
Thanks
Luigi
2017-04-19 16:14 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi Nicolas,
>
>
Hi Nicolas,
Try to remove the parentheses:
MATCH {class: Pokemon, as: p}.inE('has_type').outV(){class: Type, as: t}
RETURN p, t
In the meantime I'll check why it doesn't work (it should...)
Thanks
Luigi
2017-04-19 16:01 GMT+02:00 nicolas treiber :
> Hi,
>
> I
bt if we have more then one dependent Vertex
> then how we will put it into the same query like Server IsMountedOn Storage
> and Server IsConnectedTo Network.
>
> On Tuesday, April 18, 2017 at 6:07:35 PM UTC+5:30, Luigi Dell'Aquila wrote:
>>
>> OK, got it, if you only need the RIDs of
riting Select * from User and we will get all
> the details of User.
>
> Hope you are understand what I am actually looking for.
>
> Thanks
> Chaitanya
>
> On Tuesday, April 18, 2017 at 5:42:31 PM UTC+5:30, Luigi Dell'Aquila wrote:
>>
>> Hi,
>>
Hi,
A MATCH statement is what you need:
MATCH
{as:user} -Performs-> {as:process} -Uses->
{class:Application, as:app, where:(applicationName = ?)} -RunsOn->
{class:Server, as:server, where:(osType = ?)}
RETURN user.name, process.id, app.name, server.url, server.name
/* just add here all the
Hi Nicolas
I'm not sure I understood the data format you expect as a result:
ex 1:
vegetal, tree, green
vegetal, tree, brown
vegetal, flower, green
vegetal, flower, yellow
ex 2:
vegetal, tree, [green, brown]
vegetal, flower, [green, yellow]
or anoother one?
Thanks
Luigi
2017-04-13 20:02
Hi Nicolas,
You can try the following query:
SELECT @rid as student, out("has") as mark from (
SELECT FROM Student ORDER BY avg_mark DESC LIMIT 3
) UNWIND mark
Thanks
Luigi
2017-04-13 14:15 GMT+02:00 nicolas treiber :
> Hi.
> I'm pretty sure that what i want
ass: File, as: file, optional: true} RETURN
> parent, child, file
> But it does not wok because "optional" must be at the end of a match
> chain... Any idea of a workaround for that ?
>
> Le dimanche 2 avril 2017 11:24:34 UTC+2, Luigi Dell'Aquila a écrit :
>>
>>
)
Thanks
Luigi
2017-04-02 11:22 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi Nicolas,
>
> I'm afraid it's not supported yet, you can work around it with a
> SELECT/MATCH like follows:
>
> SELECT FROM (
> MATCH {class: Folder, as: parent}.outE
Hi Nicolas,
I'm afraid it's not supported yet, you can work around it with a
SELECT/MATCH like follows:
SELECT FROM (
MATCH {class: Folder, as: parent}.outE("parent_of"){as: theEdge,
optional: true} RETURN parent, theEdge, theEdge.in() as child
) UNWIND child
I hope it helps
Thanks
Luigi
Hi Shanlie,
Do you mean a custom ordering (first records with 3, then with 2 and so on)?
No it's not currently supported, but you can open an issue for this, we'll
consider it for an enhancement in next releases
Thanks
Luigi
2017-03-31 13:58 GMT+02:00 Shanlie Suresh :
Hi Alexander,
Do you have a script to create a db (or a db dump) that reproduces the
problem?
Thanks
Luigi
2017-03-21 21:30 GMT+01:00 Alexander Dederer :
> Good day!
>
> I try use orientdb-community-2.2.17 and check is OrientDB ok for for our
> Product or not.
> But
Hi Luis,
In general this should not happen. Could you please add some info about the
process:
- which OrientDB version are you using?
- how are you inserting/deleting data? (binary API, SQL)
- are you working in tx or noTx?
Thanks
Luigi
2017-03-21 13:21 GMT+01:00 Luis Angel Hernández Acosta
se that's a win-win for
> all of us!
>
> -- John
>
> On Thursday, March 16, 2017 at 9:46:57 AM UTC-4, Luigi Dell'Aquila wrote:
>>
>> Hi John,
>>
>> In MATCH statement (2.2) and more in general in 3.0 we are changing the
>> optimization of queries based o
ks.
>
> Thanks!
>
> -- John
>
> On Mar 16, 2017, at 07:24, Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>
> wrote:
>
> Hi John,
>
> you have two alternatives:
>
> 1) use OrientVertex.countEdges() to check which of the two vertices has a
> smaller number of
Hi John,
you have two alternatives:
1) use OrientVertex.countEdges() to check which of the two vertices has a
smaller number of edges. This approach is good if you know that at most one
is a supernode
2) if you know that both vertices can be supernodes, then the only
efficient way to find the
Hi,
A link is just a physical pointer, eg.
Record 1: {@rid: #12:0, name:"John" }
Record 2: {@rid: #12:1, name:"Frank", friendOf:#12:0 }
the friendOf attribute here is a link. Given Record 2, you can easily find
Record 1 following the link, but if you only know Record 1 you have no
information
Hi Tore,
Sorry, we are super busy to release the first preview of 3.0, but it's not
an excuse.
I'll check it with the team and see if we have an ETA
Thanks
Luigi
2017-03-08 10:47 GMT+01:00 'scott molinari' via OrientDB <
orient-database@googlegroups.com>:
> This issue?
>
>
gt;
> On Monday, January 23, 2017 at 3:51:54 AM UTC-5, Luigi Dell'Aquila wrote:
>
>> About details and docs, many things will be updated in next few days and
>> released with the M1
>>
> --
>
> ---
> You received this message because you are subscribed to the Goog
Hi Muhammad,
Probably a mix of SELECT and MATCH will do the trick:
SELECT count(gift) as count, a, b from (
MATCH
{class:User, as:a, where:(name = 'User A')} -Shared-> {as:gift} -With->
{class:User, as:b, where:(name = 'User b')}
RETURN $patterns
) group by a, b
Just put in the WHERE
Hi,
You can create a List and store it as a property value, eg.
OrientVertex v = ...
List values = new ArrayList();
for(...){
ODocument item = new ODocument("Bid");
item.field("bid", 5.01);
item.field("buyer", buyer);
values.add(item);
}
v.setProperty("bids", values);
Just make sure
Hi Suyog,
Typically with SSD you will have better performance.
Thanks
Luigi
2017-02-16 5:04 GMT+01:00 Suyog Kale :
> Is there any disadvantage using Persistent disk than SSD persistent disk
> for OrientDB data storage?
>
> On Wednesday, 8 February 2017 09:53:51
Hi Ravikanth,
I'm not sure I understood your use case, but probably you should consider
MATCH statement (http://orientdb.com/docs/2.2.x/SQL-Match.html) instead of
TRAVERSE
Thanks
Luigi
2017-02-03 8:04 GMT+01:00 Ravikanth Koride :
> Hi,
>
> We are creating a item
Hi Scott,
We are writing down some specific docs (new features and migration guide),
they will be available in next very few days
Thanks
Luigi
2017-02-01 8:55 GMT+01:00 'scott molinari' via OrientDB <
orient-database@googlegroups.com>:
> Morning Luigi!
>
> Thanks for the clarification.
>
>
Hi Scott,
It just stands for milestone 1 ;-)
Luigi
Il 1 feb 2017 05:39, "'scott molinari' via OrientDB" <
orient-database@googlegroups.com> ha scritto:
> I noticed it mentioned by Luca and Luigi and was just wondering.
>
> Scott
>
> --
>
> ---
> You received this message because you are
Hi Hartmut,
It seems to be a bug, could you please file an issue about this?
Thanks
Luigi
2017-01-28 10:08 GMT+01:00 hartmut bischoff :
> I observed a strange behavior of simple Arrays
>
> On a schemaless db, when I perform an update like
>
> UPDATE #18:4 set abc =
Hi Alberto,
please try to replace this
OSequenceLibrary sequenceLibrary = access.graph.getRawGraph().getMetadata().
getSequenceLibrary();
with this
OMetadata md = access.graph.getRawGraph().getMetadata();
md.reload();
OSequenceLibrary sequenceLibrary = md.getSequenceLibrary();
Maybe it's just
your
> fix made into 2.2.15 or shall I submit a bug?
>
> Thanks,
>
>
> On Tuesday, January 3, 2017 at 1:23:18 PM UTC-8, Borov wrote:
>>
>> Thanks for fixing it Luigi.
>>
>>
>> On Monday, January 2, 2017 at 2:19:56 AM UTC-8, Luigi Dell'Aquila wrote:
>>>
ions)?
>
> I can't figure out by the roadmap, issues for 3.0, or the 3.0
> documentation whether SQL can be participate in a transaction along side
> the graph api.
>
> On Thursday, July 14, 2016 at 2:22:17 AM UTC-4, Luigi Dell'Aquila wrote:
>>
>> Hi,
>>
>&
Hi Pete
You can find my answer on SO
Thanks
Luigi
2017-01-16 19:36 GMT+01:00 Peter Figliozzi :
> I would like to retrieve all vertices in a SQL query that have at least
> one connection (non-zero degree). Just returning the rid is probably OK,
> but it would be nice
Hi guys,
I just pushed a fix on branch 2.2.x
Thanks
Luigi
2017-01-02 10:19 GMT+01:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi guys,
>
> You're right, the old executor supported it but the parser does not
> correctly parse it. I think I can easily support it, I
Hi guys,
You're right, the old executor supported it but the parser does not
correctly parse it. I think I can easily support it, I'm checking it now.
I'll keep you posted
Thanks
Luigi
2016-12-31 17:48 GMT+01:00 hartmut bischoff :
>
> select ... where gives an array,
Hi,
the OClass class has two methods:
- getSubclasses() that returns the direct subclasses
- getAllSubclasses() that returns all the class hierarchy under current
class
to get the OClass you can use the following:
ODatabaseDocument*: db.getMetadata().getSchema().getClass("className")
uture readers, I believe the second "WHERE" in suggested
> SQL statement should be an AND.
>
> Thank you very much for the quick and helpful response!
>
> -- John
>
> On Friday, December 23, 2016 at 2:33:49 AM UTC-5, Luigi Dell'Aquila wrote:
>>
>> Hi John,
>
Hi John,
You can try with the following:
SELECT FROM YourClass where key = :k where in('Child') contains :p
in a situation where you have supernodes it will be faster, but of course
it will be a bit slower when you have small fan out
Thanks
Luigi
2016-12-22 20:57 GMT+01:00 John J. Szucs
Hi Jayaraj,
Ar you working remotely? Current implementation does not support mixed
remote transactions (APIs and SQL together, see
http://orientdb.com/docs/2.2.x/Transactions.html).
This will be supported in next v 3.0
Anyway, v 2.0.x is no longer supported and definitely much less stable than
Hi Gregory,
Are you on windows, linux or mac (or other)?
Thanks
Luigi
2016-12-21 12:31 GMT+01:00 Gregory Mace :
> this happens when I try to put orientdb-spatial jar file in the ./lib
> directory.
> I'm running v2.2.13 server and using : orientdb-spatial-2.2.13.jar
>
>
Hi,
It's very similar, but not actually the same ;-)
One has
else if (context.compareTo(value) < 0)
The other one has
else if (context.compareTo(value) > 0)
(see the greater-than vs. less-than)
The //BIGGER comment in one case is wrong of course.
I'm looking at the source code in 2.2.x
Do you mean the network binary protocol?
Thanks
Luigi
2016-12-07 14:01 GMT+01:00 'scott molinari' via OrientDB <
orient-database@googlegroups.com>:
> Nevermind. I've got it!
>
> Scott
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB"
Hi Eric,
In a schemaless/mixed schema it's hard to make assumptions, but something
can be optimized of course.
Probably the big part of the difference is due to the number of traversed
edges (N at the first level, NxN at the second, probably), but part of that
can also be due to internal
Hi Tomas,
Try to replace WHILE $depth <= 2 with MAXDEPTH 2
You should see an important improvement. The difference is that with WHILE
condition the TRAVERSE also does the 3rd level traversal and then checks
the condition, while with a MAXDEPTH it just stops at the specified level.
Thanks
Luigi
Hi,
The ODocument is managed as a java Map, so it does not preserve field
order, I'm afraid what you need is not supported out of the box
Thanks
Luigi
2016-11-25 9:19 GMT+01:00 Academia Learning Centro de inglés y de formación
:
> HELP
>
> El miércoles, 23 de
Hi,
The only difference is that CREATE VERTX also checks that the target class
is a vertex class. All the rest is exactly the same
Thanks
Luigi
2016-11-23 8:48 GMT+01:00 Jyothis K P :
> What is the difference between INSERT and CREATE VERTEX in OrientDB?
>
Hi,
by default OrientDB Studio Graph panel displays only 20 records. You can
override this behavior adding a "limit" at the end of the query, eg.
SELECT FROM V LIMIT -1
Thanks
Luigi
2016-11-22 12:03 GMT+01:00 'Hans-Jürgen Otto' via OrientDB <
orient-database@googlegroups.com>:
> Hey guys,
>
Hi,
I'm not sure I understood your use case, but I think what you need is
something like
select service_name from (
select
expand(out('store_has_service_group')['is_deleted =
false'].out('service_group_has_store_service'))
from #48:999
) WHERE ...
Thanks
Luigi
2016-11-19 7:05 GMT+01:00
Hi Gopinath,
This issue could be due to some caching mechanisms. Could you please add a
vertex.getRecord().reload()
after fetching the record? If it solves the problem, then it's likely a
cache problem
Thanks
Luigi
2016-11-16 13:53 GMT+01:00 :
> Hi,
> I have
Hi,
What is EHR_Status? Is it a link property?
In general the answer is yes, you can mix document and graph models and you
should have no problems with this, so I suppose there is something else...
Thanks
Luigi
2016-11-16 11:10 GMT+01:00 Academia Learning Centro de inglés y de
formación
Hi
That's the right syntax, it's supposed to work fine.
Could you please post a simple script to create a db that reproduces the
problem?
Thanks
Luigi
2016-11-16 10:58 GMT+01:00 Academia Learning Centro de inglés y de
formación :
> Hi,
>
> I have this vertex of
Hi Gopinath,
This is a very basic operation and your code seems to be correct, so I
suspect there is a problem somewhere else.
Just a couple of questions:
- are you always using NoTx? In this case, why are you invoking
graph.commit()? there is no need for that.
- how do you create your schema?
-
Another question, are you passing actual RIDs as parameters? If you pass
strings it won't work
Thanks
Luigi
2016-11-14 16:19 GMT+01:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi,
>
> Which version are you working with?
>
> Thanks
>
> Luigi
>
>
&
Hi,
Which version are you working with?
Thanks
Luigi
2016-11-14 16:12 GMT+01:00 Borov :
> Hi guys,
>
> I'm not sure what am I doing wrong when trying to create an edge from one
> rid to another. Here is the syntax that doesn't work:
>
> String sql = "create edge
Hi,
The result of a subquery is a result-set, not a single element. I think
that rewriting the query this way it should work fine:
select from B let $aa = (select from A where id = 1) where $aa contains a
Thanks
Luigi
2016-10-26 8:43 GMT+02:00 Oleksandr Gubchenko :
>
Hi,
I'm not sure I got the point, could you please post a script to create a DB
and reproduce the problem?
By default, the expand() function returns the full record, so that should
be enough for what you need.
Thanks
Luigi
2016-10-26 7:46 GMT+02:00 :
> Unfortunately it
Hi Anthony,
Probably we will implement this in the future, but for now you have to do
the query on the comments and then manually traverse the relationship.
Current LiveQuery implementation still needs some optimizations, query
de-duplication is one of these ;-)
Thanks
Luigi
2016-10-19 21:37
Hi,
Currently the is no namespace concept in OrientDB, so I'm afraid you have
to use a custom naming convention for it, eg. namepsace_ClassName
There is an old issue about this
https://github.com/orientechnologies/orientdb/issues/3854
but it's not in the roadmap for now. If it's a compelling
Yes, please
Thanks
Luigi
2016-10-13 18:23 GMT+02:00 <borov...@gmail.com>:
> Thanks Luigi. Shall it be filed as a bug?
>
>
>
> On Wednesday, October 12, 2016 at 11:58:33 PM UTC-7, Luigi Dell'Aquila
> wrote:
>>
>> Hi guys,
>>
>> Ok, it's corr
Hi guys,
Ok, it's correct, it "kind of" works because of some internal corner cases,
but it's definitely a dirty work around :-D
Anyway, I'll fix the main problem in next days
Thanks
Luigi
2016-10-13 7:37 GMT+02:00 :
> Hi Oleksandr,
>
> Interesting, I think it is similar
Hi Anthony,
2016-10-12 19:46 GMT+02:00 Anthony :
> @Luigi, thanks so much for your detailed response. Overall, these are
> encouraging comments. A few follow-up queries, if I may:
>
>>
- Are there any limitations on the types of queries with which
LiveQuery
Hi Anthony,
As Luca mentioned above, LiveQuery is a new feature, so it has some
limitations, but on the other hand you can expect important improvements in
the near future.
The fact that RethinkDB did not manage to survive as a company IMHO depends
on the business model, not on the product
. However, should I
> submit it as a bug orientDB team or is it something you working on to
> change in 3.0?
>
>
>
> On Tuesday, October 11, 2016 at 1:00:19 AM UTC-7, Luigi Dell'Aquila wrote:
>>
>> Hi,
>>
>> It seems there is a bug in the parser, but to be
Hi,
It seems there is a bug in the parser, but to be honest I really hate that
syntax, it's not clear, not elegant and IMHO also misleading.
You can try this:
update #25:0 set settings.classTemplate.template2 = 'bbb'
it has the exact same semantics, but it's clear and straight forward.
Thanks
Hi,
this seems to be a bug, could you please open an issue here
https://github.com/orientechnologies/orientdb/issues/
Thanks
Luigi
2016-10-04 6:58 GMT+02:00 :
> Hi guys,
>
> I hope I'm doing something wrong and it's not a shortcoming for the
> orientdb's functionality.
e a place for you.
>
> I'll send you an email with further details.
>
> LynnBender
> http://twitter.com/linearb
> http://www.linkedin.com/in/lynnbender/
>
> -
>
>
> On Fri, Sep 30, 2016 at 11:54 PM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wro
Hi Luca,
Do they have a deadline for the submission? I couldn't find it on the
website.
For a specific event like that we need to prepare the session very well and
it has to be on some bleeding edge improvement or on a hot topic.
I don't know if it's affordable for us to invest on an
Hi Jonathan,
That's quite strange, it seems to be a bug. Could you please report an
issue here?
https://github.com/orientechnologies/orientdb/issues
Thanks
Luigi
2016-09-23 22:56 GMT+02:00 :
> I want to use MATCH to find pairs of nodes that share two other nodes. I
Hi Scott,
I'm not sure about this (I don't manage the PHP stuff) but I think it does.
Thanks
Luigi
2016-09-22 7:15 GMT+02:00 'scott molinari' via OrientDB <
orient-database@googlegroups.com>:
> A polite bump.
>
> Scott
>
> --
>
> ---
> You received this message because you are subscribed to
Hi guys, I just pushed a fix for this on 2.2.x
Thanks
Luigi
2016-09-14 12:11 GMT+02:00 'scott molinari' via OrientDB <
orient-database@googlegroups.com>:
> Thanks Alessandro!
>
> Scott
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB"
Hi Daniele,
Maybe I'm wrong, but if I remember well BaasBox uses links, not edges to
represent relationships.
I don't know the exact domain, so I cannot give you a migration procedure,
but I think you should write one to convert links to edges
Thanks
Luigi
2016-09-15 18:20 GMT+02:00 Ivan
Hi Lui,
OrientDB performs aggregate operations in memory, so in this case you just
have to give it some more heap memory. To do it, just edit the server.sh
and set -Xmx to 1024 or 2048, it should be enough
Thanks
Luigi
2016-09-08 19:14 GMT+02:00 'Lui Neumann' via OrientDB <
Hi William,
If you are using OrientDB v 2.2 you should consider using MATCH statement:
http://orientdb.com/docs/2.2.x/SQL-Match.html
It is a much better fit for this kind of queries.
I hope it helps
Thanks
Luigi
2016-09-07 19:30 GMT+02:00 William :
> Hi,
>
> I'm new to
Hi Scott
The client is always the client application (as for single node)
Thanks
Luigi
2016-08-18 11:25 GMT+02:00 'scott molinari' via OrientDB <
orient-database@googlegroups.com>:
> Hoooh!!! :-)
>
>
> Scott
>
> --
>
> ---
> You received this message because you are subscribed to the
Hi,
well, these two drivers are for two different languages. phpOrient is for
PHP and OrientJS is for Node.js, so I'd choose based on your preference
language.
Both drivers are well supported, OrientJS is maintained internally,
phpOrient is maintained by Ostico that is an external contributor,
Hi Abhijit,
Do you have a test case to reproduce the problem?
Thanks
Luigi
2016-08-17 6:00 GMT+02:00 Abhijit Shivathare :
> Error is : Unhandled rejection OrientDB.RequestError: Lexical error at
> line 1, column 35. Encountered: "\\" (92), after : "
> when I
Hi Mike
To remove a specific custom property you can set it to null:
ALTER PROPERTY Foo.bar custom baz=null
To remove all the properties you can use "custom clear":
ALTER PROPERTY Foo.bar custom clear
There is a regression with this last statement in v 2.2.7, but it's already
fixed; the fix
Hi Suyog,
Did you save it before executing?
If you are running distributed, there is a known issue in v 2.2.6 about
this. The fix will be released in a few hours with 2.2.7
Thanks
Luigi
2016-08-11 13:27 GMT+02:00 Suyog Kale :
> Hello,
>
> There is some issue with my
undException: com.sun.jna.Platform
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(
Hi Krishna,
Sure, OrientDB supports remote connections via Blueprint API. See
http://orientdb.com/docs/2.2.x/Graph-Database-Tinkerpop.html#getting-started-with-blueprints
When migrating from Neo4j probably you will find some small differences,
but the standard APIs are the same
Thanks
Luigi
Hi Erik,
The block with
if (textUpperCase.startsWith("SELECT") && false) {
is never executed (see the && false), it's there because of some tests, but
it's disabled for a reason.
The problem here seems to be in class loading, the SQL engine cannot find
the factory that creates the executor for
Hi,
What do you mean exactly? If you use schemaless approach, different
vertices can have different properties of different types.
You just have to avoid defining properties in the schema
Thanks
Luigi
2016-08-03 10:02 GMT+02:00 parvat :
> Hi, Can you help me on the
com>:
> It means cant we create a unidirectional edge?
>
> On Friday, July 29, 2016 at 1:24:23 PM UTC+5:30, Luigi Dell'Aquila wrote:
>>
>> Hi,
>>
>> Every edge in OrientDB is bi-directional, meaning that you can traverse
>> it in both directions.
>>
Hi,
Every edge in OrientDB is bi-directional, meaning that you can traverse it
in both directions.
There is no way to create an edge with no direction, but you can always use
.both() operator to traverse all the edges, regardless the direction
Thanks
Luigi
2016-07-29 9:52 GMT+02:00 parvat
Of course this is true only if the parent class is empty, otherwise you
have to define a non-unique index on the parent class as well
Thanks
Luigi
2016-07-28 8:58 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> There is just no need to define indexes on the parent class
There is just no need to define indexes on the parent class, as long as you
have indexes on the same properties on the subclass.
Eg. if you have a class A with two subclasses A1 and A2 and both subclasses
have an index on "name", if you do a
SELECT FROM A WHERE name = 'foo'
it will use the
101 - 200 of 618 matches
Mail list logo