Giraldo,
Thanks for the info. I haven't hit any issues yet but good to have this
information so when I hit it, I'll be ready.
On Wednesday, January 15, 2014 5:06:02 PM UTC+2, Giraldo Rosales wrote:
>
> Andrey
> Thanks! WIll have to check it out.
>
> SHak
> Glad it worked out. Hopefully they update it soon. We are just using the
> queries. The only suggestion is to watch for the parameters. First, adding
> parameters was not documented well. Anyone looking to add them, you have to
> use:
> db.command(query, {'params':{}}, callback);
>
> Then you can either use the object or array types described on the
> OrientDB site. Now the problems come in on the parsing of those params.
> There is some inconsistency and bugs on OrientDB side... RecordID formats
> differ between SELECT, INSERT, and UPDATE. Some throw an error with quotes
> around the RecordID, some don't. OrientDB has not yet implemented
> parameters in sub-queries. This is very bad since it is heavily used. Since
> we are to check and parse our own parameters for sub-queries, it would be
> nice for the node-orientdb module to just insert the params for us and send
> it off to the database.
>
> I did find one solution that you might want to also modify in the
> node-orientdb files... In the file,
> "/orientdb/lib/orientdb/connection/parser.js", around line 320, comment out
> the four lines below:
> //if(REGEXP_RID.test(value)) {
> // result = result.concat(value);
> //} else {
> //***Leave the following line***
> result = result.concat(...
> //}
>
> Seems to fix some of the RecordID parameter problems. Before the change,
> the RecordID would not be quoted and would corrupt the object being sent to
> the db if the RID property was at the beginning of an object. For example:
> {'rid':#10:1, 'name':'Java'}
>
> Notice the uncommented RID has an exposed ":" that throws off the object.
>
> Giraldo
>
>
> On Wednesday, January 15, 2014 3:55:24 AM UTC-5, Andrey Lomakin wrote:
>>
>> Hi guys,
>> Few cents from me, I know that people use nodejs-java bridge for OrientDB
>> without problems look at https://github.com/joeferner/node-java
>>
>>
>> On Wed, Jan 15, 2014 at 10:49 AM, SHak <[email protected]> wrote:
>>
>>> I gave node-orientdb a try; there are no problems with running
>>> Queries/Commands but trying to use *graphdb.createVertex() *did not
>>> correctly create the data in the proper class. At first I had an error
>>> *"Class
>>> 'User' is not an instance of V"*, I changed the driver code to fix this
>>> error (as described below). That fixed the exception and did create a
>>> record, however that record is not in the proper Class. So I'm sticking to
>>> user SQL Queries for now. Too bad. I really wanted to play with some of the
>>> other functions.
>>>
>>> var VERTEX_CLASS_NAME = "V";
>>> var EDGE_CLASS_NAME = "E";
>>> instead of
>>>
>>> var VERTEX_CLASS_NAME = "OGraphVertex";
>>> var EDGE_CLASS_NAME = "OGraphEdge";
>>>
>>>
>>>
>>> On Tuesday, January 14, 2014 4:40:32 PM UTC+2, Giraldo Rosales wrote:
>>>>
>>>> We are using the binary version (https://github.com/
>>>> gabipetrovay/node-orientdb). The orientdb-js using the http requests
>>>> and is using the JavaScript API bundled with OrientDB. And hasn't been
>>>> updated since Sep 8th 2011. Although node-orientdb is a bit dated, it
>>>> isn't
>>>> as dated as the orientdb-js version. The developers on node-orientdb do
>>>> not
>>>> seem to be motivated to update it until they have their own personal need
>>>> (stated by them in another post). They are still using OrientDB 1.3. So I
>>>> wouldn't expect updates anytime soon unless someone else takes over.
>>>>
>>>> We are able to accomplish most tasks using sql with the command action
>>>> using node-orientdb. The missing functionality seems to be:
>>>>
>>>> - RECORD_CHANGE_IDENTITY
>>>> - RECORD_CLEAN_OUT
>>>> - POSITIONS_FLOOR
>>>> - POSITIONS_CEILING
>>>> - PUSH_RECORD
>>>> - PUSH_DISTRIB_CONFIG
>>>> - DB_COPY
>>>> - REPLICATION
>>>> - CLUSTER
>>>>
>>>> Hopefully it is updated soon but if your project isn't dependent on the
>>>> above, you should be ok.
>>>>
>>>>
>>>>
>>>>
>>>> On Tuesday, January 14, 2014 8:57:19 AM UTC-5, SHak wrote:
>>>>>
>>>>> here is another one that I found https://github.com/
>>>>> orientechnologies/orientdb-js sadly the author did not put any
>>>>> detail on the page which normally would make me move on to something
>>>>> else.
>>>>> However, I found this wiki on orientDB page regarding this code.
>>>>>
>>>>> here is the wiki:
>>>>> https://github.com/orientechnologies/orientdb-js/wiki
>>>>>
>>>>> I was able to run SQL requests without any trouble, though it has many
>>>>> more features that I will investigate further today.
>>>>>
>>>> --
>>>
>>> ---
>>> 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/groups/opt_out.
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey Lomakin.
>>
>> Orient Technologies
>> the Company behind OrientDB
>>
>>
--
---
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/groups/opt_out.
