[orientdb] Re: SQL delete oldest edge

Thanks for your help Alessandro, your last suggestion was certainly the best, but still much too slow during batch processing. Unfortunately I think I am going to have to scrap this idea and just delete all the edges using delete edge a_relates_b from #12:0 which is really fast. Then recreate

[orientdb] ostico/phporient socket connection error in centos

*Hi,* I am using ostico/phporient official driver it will work fine in windows but not working in centos. the below error was *thrown*. *Fatal error*: Uncaught exception 'PhpOrient\Exceptions\SocketException' with message 'Error 111 : Connection refused ' in

[orientdb] Prepared Statement with params

OrientDB v2.1.2 I see from documentation that I can run a prepared query with parameters using: OSQLSynchQuery query = new OSQLSynchQuery("select from Profile where name = ? and surname = ?"); List result = database.command(query).execute("Barack", "Obama"); However I cannot seem to run a

Re: [orientdb] Massive Insert of Edges

I think I now better understand what you meant by - do I need to do batching... indeed if I actually SAVE the edges and only call commit at the very end performance remains constant (does not drop to zero) graph.addEdge("class:from_relates_to", fromVertex , toVertex ,

[orientdb] Re: Collate "Case Insensitive" is not effective on GROUP BY

Hi, case insensitive is only used for comparisons and not with group by. You can use the field name in the capital letters. Could help the following query ? select name,count(*) from (select name.toUpperCase() from Person) group by name Alessandro -- --- You received this message because

Re: [orientdb] Massive Insert of Edges

Further investigation reveals that the graph.commits are happening exactly when the 'edge per second' drops to zero, furthermore until the commit is complete the database is completely unusable! What on earth am I doing wrong, I had hoped these inserts would all be happening in the

[orientdb] Collate "Case Insensitive" is not effective on GROUP BY

Hi, Recently i found out that Class Property Setting "Collate" > "Case Insensitive" will make filter conditions case insensitive, which is great. However, I observed that it is not effective on GROUP BY clause. e.g. SELECT name, COUNT(*) as count FROM Person GROUP BY name This gives me the

Re: [orientdb] live query with graph database

Thank for the answer Luigi, thisi is absolutely game changing feature finally enabling event driven architecture have a nice day Il giorno mercoledì 14 ottobre 2015 18:03:34 UTC+2, Luigi Dell'Aquila ha scritto: > > Hi Enrico, > > Current LiveQuery implementation works at single

Re: [orientdb] [announcement] Moving to StackOverflow!

Hi Luca. For question-answering StackOverflow is the best, but which is the channel for announcements? Imagine that someone, not belonging to the Orient team, wants to spread to the community something of interest. It may be a talk, a use case, a library or a product gravitating around OrientDB.

[orientdb] Re: Collate "Case Insensitive" is not effective on GROUP BY

Ok i now realize this leads to the question on which value to present for "name" when its aggregated case insensitively. I guess i will have to go for an outer query for this. On Thursday, October 15, 2015 at 12:57:49 PM UTC+5:30, Chandima Jayawickrema wrote: > > Hi, > > Recently i found out

[orientdb] Re: Cannot open local storage with mode=rw

The database remains open. In order to close all the storage call Orient.instance().closeAllStorages(); Lvc@ On Friday, 2 October 2015 19:30:12 UTC+2, Tsadok Levi Firseck wrote: > > Hi, > > I'm using JMeter to run against a OrientDb database. > > I've already managed to connect to the

Re: [orientdb] Prepared Statement with params

Do you have the complete, full exception? Best Regards, Luca Garulli Founder & CEO OrientDB On 15 October 2015 at 13:56, Simon White wrote: > OrientDB v2.1.2 > > I see from documentation that I can run a prepared query with

Re: [orientdb] Prepared Statement with params

com.orientechnologies.orient.core.exception.OCommandExecutionException: Error on execution of command: sql.delete edge a_links_b from :vertexparam at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.executeCommand(OAbstractPaginatedStorage.java:1482) at

Re: [orientdb] Prepared Statement with params

Looks like my string ORID representation is incorrect but I have no idea what it should be... is this documented? -- --- 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

[orientdb] ETL Configuration for embedded documents

i am using document db for loaded in ETL configuration , want to embed some documents. Can you please give some suggestions or samples -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails

[orientdb] Strange behaviour on UPDATE in distributed mode: number of updated records

hi all! I have a scheme-less class in my DB, let's say it called 'testClass', it's pretty simple and contains 1 boolean property: { lock : 'true' } When I execute update query via console or web ui: update testClass set lock = true i've got Updated record(s) '1' in 0.033000 sec(s).

[orientdb] Populate a linklist in a batch command via LET blocks

Hello, I'm currently trying to get this sql batch command to work: BEGIN LET adverse_event = CREATE VERTEX AdverseEvent set name = "sneeze" LET adverse_event_2 = CREATE VERTEX AdverseEvent set name = "cough" LET report = CREATE VERTEX Report SET adverse_events = [ $adverse_event.@rid,