I'm using the Orient Studio browse page for basic SQL commands and writing functions in Javascript when necessary (since I don't know any Java), but I'm assuming that's not going to make a difference for memory errors or command parsing, right?
Also earlier I said that "DELETE VERTEX MyVertex LIMIT 100" didn't work, but that wasn't entirely accurate--it was the following query that was giving me the GC memory error: "DELETE VERTEX MyVertex WHERE property1 IS NULL LIMIT 100" Still, I don't see why the LIMIT option wouldn't work in conjunction with WHERE. Any ideas? On Wednesday, August 12, 2015 at 5:23:21 AM UTC-4, [email protected] wrote: > > Hi, > I tried to cancel 3,000,000 of vertices with this java code and I had no > problems. > for(int j=0;j<30000;j++){ > g.command(new OCommandSQL("DELETE VERTEX MyVertex LIMIT 100")).execute(); > g.commit(); > } > > Let me know how it goes. > > Regards, > Alessandro. > -- --- 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/d/optout.
