Hi Eswar,
You can always find latest stable version here
http://orientdb.com/download/
This version is preferred for production purposes.
Note: if you hold for a few hours you'll find 2.2.6, we are releasing it
now ;-)
Thanks
Luigi
2016-07-28 8:35 GMT+02:00 eswar reddy
Hi Hartmut,
There is no specific configuration to specify that an index is unique at
class level, but you can just avoid to define the index on the superclass,
as the query engine will use the subclasses index if needed (first level
inheritance only)
Thanks
Luigi
2016-07-28 7:07 GMT+02:00
Here you can find the answer:
http://orientdb.com/docs/2.2.x/Release-2.2.0.html#sql-and-console-commands-changes
Please try the following:
alter database CLUSTERSELECTION "round-robin"
Thanks
Luigi
2016-07-26 5:51 GMT+02:00 Luca Garulli :
> I think there is an error
A script can be a simple sequence of SQL commands, that will be executed on
an empty, newly created db, with a very strict configuration (eg. with
given number of clusters per class) to make sure that all the clusters are
created in the exact same way
Thanks
Luigi
2016-07-25 10:29 GMT+02:00
Hi Scott,
Unfortunately you cannot force RID generation, even from binary interfaces.
Creating and detaching a node is an option, but I don't think it's the most
effective one. IMHO a simple db backup/restore will do the trick in a much
more efficient way
Thanks
Luigi
2016-07-25 10:01
Hi Scott,
The only way to preserve RIDs now is to provide a DB backup.
As an alternative, you can provide a script that creates a db, but you have
to explicitly set the minimum clusters per class in the db config,
otherwise you will have different RIDs on machines with a different number
of
Hi,
This is our intention, so the answer is "it's very likely, but not yet
implemented, even in alpha"
Thanks
Luigi
2016-07-14 0:41 GMT+02:00 odbuser :
> Bump... this one is very important for anyone using transactions. Any
> comments?
>
>
> On Tuesday, June 21, 2016 at
Hi Paul,
I'm afraid I didn't get the point... could you please make an example?
Thanks
Luigi
2016-07-12 0:07 GMT+02:00 Paul I Bloom :
> After I create a record, I would like to use the value from one of the
> Types
>
> in that record in another record - that is have it
Hi Amrutha,
Export in SQL is not supported, but you can export your database in JSON,
edit it and then reimport
http://orientdb.com/docs/2.2/Export-and-Import.html
Thanks
Luigi
2016-07-11 20:38 GMT+02:00 Amrutha Valli :
> How can i export orientdb data as sql
Hi Fabrizio,
In my experience, there numbers seem a bit too high...
Just a couple of questions (sorry, I don't know if you already answered
before, maybe I missed it...)
- how big is your DB?
- what is your configuration? (RAM, heap, off-heap and so on)
- I see you are using out() without any
Hi Fabrizio,
That's an old bug in OrientDB Studio, it just displays the wrong engine
type (always SBTREE), but the indexes are created correctly
Thanks
Luigi
2016-07-03 17:42 GMT+02:00 Fabio Rinnone :
> Hi there,
>
> if I create different type of indexes as follow
Hi Hugo,
In v 2.2 OrientDB creates, for each class, as many clusters as the number
of cores available on your machine. This gives advantages when doing
multi-thread operations.
If you want, you can return to the previous behavior setting
minimumClusters=1 (see
30 12:48 GMT+02:00 Hartmut Bischoff <topofo...@gmail.com>:
>
>>
>>
>> Am 30.06.2016 um 09:29 schrieb Luigi Dell'Aquila:
>>
>> Hi Hartmut
>>
>> I see a backslash before a } in your request
>>
>> ret= DB.execute { 'MATCH {class:
Hi Hartmut,
I just pushed a fix for the NPE on 2.2.x branch. The fix will be released
with next 2.2.4
Thanks
Luigi
2016-06-30 9:29 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi Hartmut
>
> I see a backslash before a } in your request
>
> ret= DB.ex
Hi Hartmut
I see a backslash before a } in your request
ret= DB.execute { 'MATCH {class: Industry, as: Industries\} <-- {} <-- {
as: Subcategories } RETURN Industries, Subcategories' }
Could that be the problem?
About the NPE, I'm checking it now
Thanks
Luigi
2016-06-29 17:20 GMT+02:00
Hi Francisco,
Thank you very much for you feedback, product quality is our first goal and
the feedback from the community is always a key factor to increase it.
I'm very sorry about last point, I think I already answered you with a
private email with all the details about our services (sometimes
Hi Scott,
Exactly, we really hope this new process will help the communication
between the community/contributors and the core team. Please feel free to
comment directly on the specific issues
Thanks!
Luigi
2016-06-26 12:53 GMT+02:00 'scott molinari' via OrientDB <
Hi Francisco,
you can find the doc pages here:
https://github.com/orientechnologies/orientdb-docs/
You can open issues there or just fork the project, fix whatever you want
and send a pull request.
For the website, you can just write your suggestions on this mailing list
Thanks
Luigi
y see "votes". How does that work with
> these tickets?
>
> On Tue, Jun 21, 2016 at 9:38 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Francisco,
>>
>> To request new features, just open an issue on the main issue track
nt
If you think your request is "big" enough to deserve and OEP feel free to
suggest it in the issue description
Thanks
Luigi
2016-06-21 15:33 GMT+02:00 Francisco Reyes <franci...@natserv.net>:
> On Tuesday, June 21, 2016 at 2:52:53 AM UTC-4, Luigi Dell'Aquila wrote:
>>
&
that keeps the current
status of the proposal and the history
Thanks
Luigi Dell'Aquila
--
---
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 orie
The ETA for 3.0 is approximately the end of this year
Thanks
Luigi
2016-06-16 20:42 GMT+02:00 pabloa <pablo...@gmail.com>:
> I ll do that.
>
> do you have an ETA for for version 3.0?
>
> P
>
> On Thursday, June 16, 2016 at 12:50:40 AM UTC-7, Luigi Dell'Aquila wrote:
Hi guys,
Query cursors are one of the hot topics for 3.0 development.
In the meantime I suggest you to use RID based paging or SKIP/LIMIT
I'll check the original issue and see if I can fix it quickly
Thanks
Luigi
2016-06-16 1:48 GMT+02:00 Stuart Reynolds :
> +1
>
>
the vertex 5 is connected to vertices 6
> and 7, vertex 7 is connected to vertex 8, etc.
>
>
> Le lundi 13 juin 2016 09:38:56 UTC+2, Luigi Dell'Aquila a écrit :
>>
>> Hi,
>>
>> It's strange, with low memory you can expect some performance degradation
>>
Hi Scott,
I think you are right, and I think all the rest of OrientDB team will agree
with you. The name "cluster" is completely misleading when talking about
physical data portions.
Some time ago I proposed to use the name "data file" to refer to physical
files that contain data (that is what
Hi,
could it depend on multiple clusters per class? How many clusters does your
"industry" class have?
I tried in Studio the query
SELECT FROM OUser ORDER BY @rid DESC
and it worked fine...
Thanks
Luigi
2016-06-08 18:20 GMT+02:00 hartmut bischoff :
> Hi altogether
>
>
Hi Vijay,
Live queries are mainly designed to be used in reactive architectures,
where your application expects a push notification when something changes
instead of querying the db periodically.
For your needs, I suggest you to take a look at OrientDB hooks
; some are Regular, depending on their needs (or not) for local properties.
> --Eric
>
>
> On Tue, May 24, 2016 at 9:54 AM, Luigi Dell'Aquila <
> luigi.dellaqu...@gmail.com> wrote:
>
>> Hi Eric,
>>
>> There are no big penalties, the only real problem
>
> On Tuesday, May 24, 2016 at 8:59:11 AM UTC-5, Luigi Dell'Aquila wrote:
>>
>> Hi,
>>
>> By default all the edges are created as *regular* edges.
>>
>> This default can be changed from Studio or with an SQL statement
>> http://orientdb.com/docs/
Hi,
By default all the edges are created as *regular* edges.
This default can be changed from Studio or with an SQL statement
http://orientdb.com/docs/last/Lightweight-Edges.html
In this case, an edge is created as a lightweight edge only if it has no
properties. When you add a property to a
Hi Piotr,
If you delete vertices using Graph API (eg. DELEVE VERTEX statement) edges
will be removed as well. If you force the delete using document API (eg.
DELETE FROM ... UNSAFE) then you will have orphaned edges
Thanks
Luigi
2016-05-18 17:22 GMT+02:00 Piotr Fraś :
, and with that mixed ordering
> direction this solution does not work.
> We can also achieve our target with *ORDER BY Priority **DESD**, DueTime *
> *DESC*, so your answer is valid for us.
>
> Thank you very much again.
> David.
>
>
> El miércoles, 4 de mayo de 2016, 11:48:09 (U
Hi,
The problem here is that the result set can be sorted using the index when
you define ORDER BY Priority DESC, but when you add other conditions like
ORDER BY Priority DESC, @rid ASC then the index becomes useless and the
result set has to be sorted in memory.
For the second case (ORDER BY
Hi David,
In current release this is not supported, and structurally it's not easy to
do, so I'm afraid it will hardly enter in the roadmap (but things can
change of course...)
Thanks
Luigi
2016-05-04 1:15 GMT+02:00 :
> This might be a stupid question, but is it possible
Hi,
Happy to see that you solved the problem. I'm very curious about what you
are doing, could you share some additional info? Can we help in any way?
Thanks
Luigi
2016-05-02 23:48 GMT+02:00 Ra Long :
> Figured it out. I realized almost as soon as I submitted this that I
Hi,
In v2.2 it's definitely easy using MATCH statements (
https://github.com/orientechnologies/orientdb-docs/blob/master/SQL-Match.md)
MATCH
{class: Person, as: A, where: (name = 1)}.out(){as: B}.out(){as: C},
{as: A}.out(){as: C}.out(){as: B}
RETURN A
with a plain SQL is a bit more tricky, you
Hi Simon,
if you have to do it via SQL, you can do the following, using document
queries:
UPDATE VertexFromClass remove out_EdgeClass = where
UPDATE EdgeClass set out = VertexToClass where
UPDATE VertexToClass add out_EdgeClass = where
Of course if you have to update the "out" just invert
This is the right one
https://github.com/orientechnologies/orientdb/blob/develop/core/src/main/java/com/orientechnologies/orient/core/sql/OCommandExecutorSQLUpdate.java#L379
Thanks
Luigi
2016-04-20 18:00 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> ops, sorry... w
ops, sorry... wrong link... I'll give you the info asap
2016-04-20 17:59 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi Simon,
>
> You can take a look at the execute() method of
>
>
> https://github.com/orientechnologies/orientdb/blob/develop/g
ges?
>
> from
> A > friend > B
>
> to
> A > friend > C
>
> something like
> 1. Update B remove in friend
> 2. Update friend set out C
> 3. Update C set in friend
>
>
>
>
> On Wednesday, April 20, 2016 at 4:44:09 PM U
Hi,
Which version of OrientDB are you using? We fixed a similar problem a few
hotfix releases ago
Thanks
Luigi
2016-04-18 18:12 GMT+02:00 K Major :
> Hello,
>
> I have identified a strange behavior when using OSQL inside Java. Maybe
> I'm doing something wrong ...
>
>
Hi Pablo, you can try this:
SELECT userId, activities[type = 'excursion'] as excursionActivities from
from User unwind excursionActivities
Thanks
Luigi
2016-04-13 1:28 GMT+02:00 pabloa :
> Hello
>
> I have a class User with 2 fields in a graph database
>
> User
>
>
Hi Erik,
It's hard to give you an answer here, this is the first report we have from
a system that crashes without emitting any logs at all.
In other cases, when we had an unexpected crash with few information, it
was because of some OS related procedures (eg. process kill under heavy
load), but
sorry, missing target in the second query, the right one is
SELECT expand(in('alSV')) FROM SimpleVertex WHERE s = 'dato 2'
2016-04-04 10:49 GMT+02:00 Luigi Dell'Aquila <luigi.dellaqu...@gmail.com>:
> Hi Marcelo
>
> I think your query can be written in an easier way:
&g
Hi Marcelo
I think your query can be written in an easier way:
SELECT FROM SimpleVertex WHERE out('alSV').s CONTAINS 'dato 2'
or even better (more efficient):
SELECT expand(in('alSV')) WHERE s = 'dato 2'
Thanks
Luigi
2016-04-02 1:06 GMT+02:00 Marcelo RE :
> Hi all!
Hi Paul,
If you want it as a single json you can use fetchplans
http://orientdb.com/docs/last/OrientDB-REST.html
http://orientdb.com/docs/last/Fetching-Strategies.html
If you just need it as a flat resultset, the following query should be what
you need
TRAVERSE out("has_participant") from
Hi Kent,
Right now there is no namespace concept in OrientDB, I think there is an
old feature request about this, but it's not in the short term roadmap
Thanks
Luigi
2016-03-09 21:10 GMT+01:00 Kent Laursen :
> I have a need to build schemas that represent logical data
11, Andrey Lomakin wrote:
>>
>> Hi guys,
>>
>> FYI https://github.com/orientechnologies/orientdb/issues/1288 .
>> But it is not in our short term roadmap.
>>
>>
>> On Mon, Feb 29, 2016 at 11:27 AM Luigi Dell'Aquila <luigi.de...@gmail.com>
>
Hi Erik,
Right now there is no support for such use case, you can define an index on
both fields but it will be used only for one of them.
I can think to a hack in 2.2, using a spatial index and doing a 2D spatial
search, but again, it would be a hack.
Thanks
Luigi
2016-02-28 12:43 GMT+01:00
Hi Richard,
It's a matter of transport and language typing: when you send a command via
REST interface, all the parameters are sent as strings; on the other side,
Javascript does not allow you to define parameter types, so there is no way
to infer param types and do automatic conversion
Thanks
Hi Aaron,
Can you please post OrientDB logs? Maybe it's starting on a different port.
The security group config seems to be correct
Thanks
Luigi
2016-02-24 16:49 GMT+01:00 Aaron Close :
>
> Ok maybe I'm just not getting it. I set up an aws instance
>
>
Hi Riccardo,
We mainly added it because solving some use cases is sometimes very tricky
with SELECT and TRAVERSE only.
One example is this one
https://github.com/orientechnologies/orientdb-docs/blob/master/SQL-Match.md#real-use-case-manager-in-an-incomplete-hierarchy
Try to write a
Hi Hung,
It's quite strange, can you post a sample dataset to reproduce che problem?
Thanks
Luigi
2016-02-05 6:23 GMT+01:00 Hung Tran :
> Hi,
>
> I am using OrientDB version 2.1.8, just wonder if it's a bug in binary
> protocol or not.
>
> My query is,
>
> SELECT Status,
Hi Jörg,
Thank you very much for the pointer, batch scripts are supported in Studio
(you have to enable them from the options menu (at the bottom right corner
of the box where you write the statements), from REST API and from Document
API (use OCommandScript instead of OCommandSQL), but not in
that setting?
>
> On Tuesday, January 26, 2016 at 12:30:34 AM UTC-7, Luigi Dell'Aquila wrote:
>>
>> Hi Keith,
>>
>> in 2.1 we introduced a new, stricter parser, now valid identifiers (class
>> names, property names and so on), can only contain letters, numbers, _ and
>
Hi Lorenzo,
I think this should work:
SELECT FROM (
SELECT *, out("hasBusinessLocation")[0].* as location_ from Business
where title = ?
) WHERE location_address = ?
Thanks
Luigi
2016-01-26 0:08 GMT+01:00 Renzo Ludeña :
> Hi friends, I need your help.
> I have 1
Hi Keith,
in 2.1 we introduced a new, stricter parser, now valid identifiers (class
names, property names and so on), can only contain letters, numbers, _ and
$.
For backward compatibility, you can disable the new parsing setting
strictSql=false (see Studio -> db tab)
Thanks
Luigi
2016-01-25
Hi,
when you say "Java classes", do you mean with Object API?
If you are referring to OrientDB classes, consider that every edge and
every vertex is a document as well, so you can use it as is
Thanks
Luigi
2016-01-25 9:46 GMT+01:00 ciroBorrelli skymedia :
> dear
Hi Athanassios,
This is the expected behavior, but you can obtain what your are looking for
just adding a filter to the query:
select out() from Person where out().size() > 0
Consider that out() is a normal projection, you could have more than one,
eg.
select name as personName, out() from
Hi guys,
FIND REFERENCES command is not intended to be used in typical production
environments.
Links are unidirectional, so to find all the documents that refer to a
single RID, OrientDB has to do a full scan of the database, this is
operation will take a long time to execute.
We suggest to use
Hi Paul,
Yes, OrientDB can definitely be used from the DOM, but I'd not suggest to
put all your application logic in the client-side JS in general.
As a general advice, I suggest you to:
- connect via HTTPS
- use OrientDB authentication to make sure the client can only access
needed resources
-
Hi,
two things here:
- first of all I suggest you to update to 2.1.9, we fixed a lot of issues
since 2.1.1, so probably the problem is already solved
- if it happens again, please send us a thread dump (
http://docs.oracle.com/javase/7/docs/technotes/tools/share/jstack.html) it
will help us to
Hi,
the problem seems to be in the ".@this", but does it actually make sense?
What's the reason to have that in the query?
Thanks
Luigi
2016-01-11 19:49 GMT+01:00 Hung Tran :
> Hi,
>
> I am migrating from version 1.7.8 to version 2.1.8, the SQL below does not
> working
It seems to be a bug, could you please open an issue about this?
Thanks
Luigi
2016-01-12 10:06 GMT+01:00 :
> Hi Hung,
>
> Try this:
>
> SELECT first(eval('$TotalListsQuery[0].Count')) AS TotalLists
> LET $TotalListsQuery = (SELECT Count(1) AS Count FROM ContactList
Hi,
Yes, this happens because FIND REFERENCES is not implemented yet in the new
parser.
The fix is not complex, could you please open an issue about this?
Thanks
Luigi
2016-01-08 17:52 GMT+01:00 Hung Tran :
> Hi,
>
> I am migrating from version 1.7.8 to version 2.1.8, I
Hi,
it's quite strange, strictSql should make this kind of operations simpler.
Could you please open an issue about this?
Thanks
Luigi
2016-01-07 11:05 GMT+01:00 Hung Tran :
> Hi,
>
> I am migrating from version 1.7.8 to version 2.1.8, I get an error with
> such query in
Hi,
how are you building it? I just tried it and it seems to work fine
locally...
Thanks
Luigi
2016-01-05 12:14 GMT+01:00 :
> Hi,
> you can download the version 2.1.8 at this link
> http://orientdb.com/download/
>
> Best regards,
> Alessandro
>
> --
>
> ---
> You
Hi Aleksey,
A good model depends on both you data and the type of analysis you want to
do.
Maybe this could be a good starting point:
http://www.slideshare.net/LuigiDellAquila/orientdb-time-representation
Thanks
Luigi
2016-01-04 6:18 GMT+01:00 Aleksey Matiychenko
Hi,
probably you will find some useful info in this old thread
https://groups.google.com/forum/#!topic/orient-database/FmWfKOiJsX4
Thanks
Luigi
2015-12-30 9:14 GMT+01:00 :
>
> Hi, I am new to orientdb and Jasperreports. I have connected Jaspersoft
> Studio with
Hi Erik,
the only difference is that query() checks that you statements are
idempotent (do not modify database status), while command() is also allowed
to execute insert/update/delete.
There is no difference in terms of performance and no particular advantage
in one or the other, apart from the
Hi Erik,
The registerEntityClass(Book.class)does two things:
- register the class for the object database
- check that the class in the schema exists and in case create it
this method does the check for you, this is why it doesn't fail. This
behavior allows you to use existing databases just
Hi Erik,
please, make sure you have the "strictSql" flag enabled (Studio -> db ->
configuration -> bottom of the page)
Thanks
Luigi
2015-12-20 11:32 GMT+01:00 Erik Pragt :
> Hello Lvc,
>
> Are you sure this is fixed? I'm using OrientDB 2.1.5 and I'm still running
> into
Hi all,
New OrientDB v 2.1.8 hotfix is available on the website.
http://orientdb.com/download/
Thanks
Luigi
--
---
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
Hi Scott,
I did a quick check and I think it's missing, we should add a little note
here at least
http://orientdb.com/docs/last/SQL-Query.html#projections
Just consider that square bracket filtering is very limited, it allows to
filter only based on a single condition (eg. no AND/OR).
Thanks
Hi,
for a simple filter (single condition) you can use square bracket notation,
eg.
SELECT EXPAND(both("FriendOf")[age >= 10]) FROM #12:1
It won't use indexes anyway, it will just retrieve the root node (#12:1)
and then it will traverse edge pointers matching conditions during the
traversa
Hi,
yes, in v. 2.1 you can use named or unnamed parameters for SKIP and LIMIT,
eg.
SELECT FROM V SKIP :skipVal LIMIT :limitVal
or
SELECT FROM V SKIP ? LIMIT ?
Just make sure you have strictSql enabled (it's the default)
Thanks
Luigi
2015-12-08 10:25 GMT+01:00 kurtuluş yılmaz
Hi Scott,
Awesome! I think should can be cited in the official docs:
http://orientdb.com/docs/last/Plugins.html
Thanks
Luigi
2015-12-08 11:48 GMT+01:00 scott molinari :
> Hi,
>
> for anyone interested, I've created a Vagrant box, which automatically
> installs
Hi Mihai,
you have two solutions:
1. use fetchplan: doc.toJson("fetchPlan:*:3")
2, use UNWIND:
select *, items.* from (select *, out('E_SomeEdge') as items from ? UNWIND
items)
Luigi
2015-12-02 10:58 GMT+01:00 Mihai Ocneanu :
> Hello,
>
> I have a vertex with some
Hi Mihai,
exactly, the two methods are not equivalent in how they return results.
In case 2 you can repliace the prefix with a custom one, using AS
Thanks
Luigi
2015-12-02 12:49 GMT+01:00 Mihai Ocneanu :
> Hi Mihai,
>>
>> you have two solutions:
>> 1. use fetchplan:
Hi Chandra,
the read performance for cases 1 and 2 will likely be comparable.
The real advantage of having a hierarchy of nodes is to have a place where
you can store aggregate information instead of re-traversing all the tree
to recalculate that every time.
Could you shed some light on your
Hi,
Unfortunately in current architecture you cannot execute queries that
involve multiple databases, so I'm afraid you have to do it at application
level
Thanks
Luigi
2015-11-22 19:22 GMT+01:00 scala solist :
> I have two databases with identical scheme, that belongs
Hi Scott,
Yes, good point, simple links do not manage referential integrity, if you
delete a linked instance you should also manually maintain the link.
Thanks
Luigi
2015-11-17 14:55 GMT+01:00 scott molinari :
> Luigi,
>
> Isn't is also a point that link
Hi,
any chance to have a working test case for this? It would be much easier to
understand the problem.
Thanks
Luigi
2015-11-16 15:57 GMT+01:00 machak :
> On Friday, November 13, 2015 at 7:46:59 PM UTC+1, kanb...@gmail.com wrote:
>>
>> Hello Team
>>
>>
>>
>> I am working
vance.
>
>
> Le mercredi 14 octobre 2015 12:25:19 UTC+2, Alain a écrit :
>>
>> Just fyi, I updated the bug with the result of my tests with version
>> 2.1.3 and 2.1.4. The bug is still there (obviously since the bug is still
>> opened).
>>
>>
>>
>&
Hi Mohammad,
this is strongly discouraged with 2.0, you could have big problems with
this approach
Thanks
Luigi
2015-11-11 17:50 GMT+01:00 Mohammad Naghavi :
> Hi everybody,
> I have a situation that I wanted to know if it is possible to run orientdb
> v2.0.15 and v2.1.5
Hi Mihai,
I think the warning is only about creating edge "classes", not edge
instances. Just try to create the schema (edge classes) before, using an
OrientGraphNoTX instance
Thanks
Luigi
2015-11-03 9:17 GMT+01:00 Mihai Ocneanu :
> Hello,
>
> I'm wondering if it is
Hi Riccardo,
I just answered your question on StackOverflow. I can't make the test fail,
so I cannot try the solution, but you can try to add a
db.activateOnCurrentThread()
at the beginning of executeScriptFromFile() method
Thanks
Luigi
2015-11-03 10:31 GMT+01:00 Riccardo Tasso
reference a particular class? (so that I can NULL them and then
> remove the class)
>
> Regarding using Graph type: yes, maybe. But I really like the simple dot
> notation as it works with LINKs. I think it is very elegant. (I take my
> syntactic sugar wherever I find it)
>
>
> On F
Hi Dmitri,
Document layer does not manage link consistency, just for a matter of
performance, but Graph layer does (eg. it removes dangling edges when you
delete a vertex). My advice is to use edges instead of links, it will also
give you another advantage, that is having bi-directional traversal
Hi Harish,
Using the short name in your use case seems to be a perfect fit. This way
you will avoid all the consequences of changing class name, especially with
cluster and index names.
About property names, unfortunately there is no support for aliases right
now. Even worse, if you do an ALTER
e you say "reduce
> occurrences". So, shouldn't we catch the exception and try again in a loop
> and give up after so many attempts? I thought i've seen some code that did
> that at one point on this.
>
> On Tuesday, September 15, 2015 at 10:53:37 AM UTC-5, L
Hi Scott,
there is no practical limitation to the number of properties you can have
in a class, you just have to consider that a single document cannot be
bigger than 2GB and the schema is kept in a similar structure.
There is no direct link from data to metadata (eg. from a record to its
class)
Hi Marvin,
Two answers here ;-)
1. For sure you will have a pattern matching option in OrientDB since v.
2.2, see
https://github.com/orientechnologies/orientdb-docs/blob/master/source/SQL-Match.md
2. We are evaluating the adoption of OpenCypher, it's a very new option and
very interesting. As
Hi Pradeep,
network communication between nodes relies on Hazelcast, here you can find
a guide on how to setup SSL communication
http://docs.hazelcast.org/docs/3.5/manual/html/ssl.html
Thanks
Luigi
2015-10-21 0:44 GMT+02:00 Pradeep Gowda :
> Hi Everyone,
>
> Is there
Hi Davide,
it seems to be a bug, could you please report it in the issue tracker?
Thanks
Luigi
2015-10-20 10:31 GMT+02:00 Davide Neri :
> Hey,
> does anybody have any idea?
>
>
>
> Il giorno mercoledì 14 ottobre 2015 10:57:34 UTC+2, Davide Neri ha scritto:
>>
>> Hi!
>>
Hi Ryan,
answers below:
2015-10-20 0:00 GMT+02:00 Ryan Chazen :
> Hi
>
> I wanted to use the non-blocking java api, but
>
> 1) It seems to create a new threat for every single request? Is this right?
>
>
Could you please report this issue here:
https://github.com/orientechnologies/PhpOrient/issues
Thanks
Luigi
2015-10-15 13:46 GMT+02:00 jaya raj :
> *Hi,*
>
> I am using ostico/phporient official driver it will work fine in windows
> but not working in centos.
>
Hi Michael,
there is not general rule, just because it depends a lot on how many
requests per second will every db have, how many data it will contain, how
complex your queries are and so on.
As a rule of thumb, I would not go over a few tens of (small) databases per
instance, just because CPU,
Great, thanks
Luigi
2015-10-16 11:43 GMT+02:00 jaya raj <jackrajfurious1...@gmail.com>:
> Hi Luigi,
>
> I has opened this issue
>
> https://github.com/orientechnologies/PhpOrient/issues/13
>
>
>
>
> On Friday, October 16, 2015 at 1:33:25 PM
Hi Enrico,
Current LiveQuery implementation works at single document/vertex/edge
level, so you can use it to detect changes in your graph topology.
There is no strict integration with Blueprints API, it just works as an SQL
statement, you can just retrieve changed records, convert them to
201 - 300 of 618 matches
Mail list logo