Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error in console for seeing a binary document #5613

Closed
publicocean0 opened this issue Jan 20, 2016 · 9 comments
Closed

error in console for seeing a binary document #5613

publicocean0 opened this issue Jan 20, 2016 · 9 comments
Assignees
Milestone

Comments

@publicocean0
Copy link

version:last version

select   from #3:229                 


0 item(s) found. Query executed in 0.0 sec(s).

there are 2 errors:

  1. 0 items is wrong, because using java code the item exists
  2. impossible to see data or at least size of binary data
@publicocean0
Copy link
Author

second attempt using console

orientdb {db=streamer}> begin
Transaction 4 is running
orientdb {db=streamer tx=[0 entries]}> delete from #3:229
Delete record(s) '0' in 0,002000 sec(s).
orientdb {db=streamer tx=[0 entries]}> delete from 33:133
Delete record(s) '1' in 0,003000 sec(s).
orientdb {db=streamer tx=[0 entries]}> commit

second error Delete record(s) '0' in 0,002000 sec(s).

@publicocean0
Copy link
Author

i m making a lot of tests .... because begin , commit in java give a block of thread

@publicocean0
Copy link
Author

test 1 :

js var a=db.command('select content,@rid from #33:137'); a[0].field('content'); end;
[Started multi-line command. Type just 'end' to finish and execute]
Client side script executed in 0,123000 sec(s). Value returned is: #3:233[0, 5, 100, 100, 100, 100, 100] v1

@publicocean0
Copy link
Author

test 2:

 js var a=db.command('select content,@rid from #33:137'); a[0]; end;
[Started multi-line command. Type just 'end' to finish and execute]

Client side script executed in 0,006000 sec(s). Value returned is: #-2:0{content:#3:233,rid:#33:137} v0

@publicocean0
Copy link
Author

test 3:


js var a=db.command('select from #3:137'); a.length; end;
[Started multi-line command. Type just 'end' to finish and execute]

Client side script executed in 0,011000 sec(s). Value returned is: 0

select from #3:137

0 item(s) found. Query executed in 0.002 sec(s).

@publicocean0
Copy link
Author

Considering that the tests confirms data exists , and in my java code there is just a simple transaction for deleting binary node and parent node , i will post another graver error

the transaction is blocked in this case

@luigidellaquila
Copy link
Member

Hi @publicocean0

could the problem be related to a front-end issue? Maybe the result is just not correctly displayed. What does the record contain?

Thanks

Luigi

@publicocean0
Copy link
Author

Probably is a problem related to printing ORecordBytes document, above i showed the console result(test 1 shows the content). The problem are with ORecordBytes ... ths kind of records.
in the test above i proved that document exists : using js (calling directly java) Using console i can't find it. Also when i try to delete it , items deleted are 0.
I think it is a simply error to fix, probably in console manager is missing the code for handling OrecordBytes documents or for visualizing them. Considering if i attach the OrecordBytes to another document ... and then i try to make a select from the parent document (Odocument) it appairs

in similar way :

0   |#3:436| (size=47 b...| (size=47 bytes)                                                                                      
1   |#3:437| (size=54 b...| (size=54 bytes)                                                                                      
2   |#3:438| (size=54 b...| (size=54 bytes)                                                                                      
3   |#3:439| (size=54 b...| (size=54 bytes)                                                                                      
4   |#3:440| (size=7 by...| (size=7 bytes)     

instead if a select from #3:436 .... nothing

@tglman
Copy link
Member

tglman commented Mar 14, 2016

hi,

Added a test case and fixed, in develop.

closing.

@tglman tglman closed this as completed Mar 14, 2016
@tglman tglman added this to the 2.2.0-rc1 milestone Mar 14, 2016
@robfrank robfrank modified the milestones: 2.2.0-rc1, 2.2.0-beta2 Mar 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants