Skip Menu |

This queue is for tickets about the REST-Neo4p CPAN distribution.

Report information
The Basics
Id: 95605
Status: open
Priority: 0/
Queue: REST-Neo4p

People
Owner: maj.fortinbras [...] gmail.com
Requestors: stesin [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.2250_2
Fixed in: (no value)



Subject: Build fails 0.2250 @win8 x64 strawberry perl
Dear Mark, thank you for issueing new release! Unfortunately, it fails to build for me, here is relevant piece of the console log: ... when is experimental at D:\Perl\cpan\build\REST-Neo4p-0.2250-oQNdFU\blib\lib/REST/Neo4p/Query.pm line 378. t\006_query.t ............... 20/? # rt80343 [Conflict (409) thrown when fail is specified for create_unique on indexes]END failed--call queue aborted. # Looks like your test exited with 255 just after 47. t\006_query.t ............... Dubious, test returned 255 (wstat 65280, 0xff00) All 47 subtests passed t\007_accessors.t ........... given is experimental at D:\Perl\cpan\build\REST-Neo4p-0.2250-oQNdFU\blib\lib/REST/Neo4p/Agent.pm line 207. when is experimental at D:\Perl\cpan\build\REST-Neo4p-0.2250-oQNdFU\blib\lib/REST/Neo4p/Agent.pm line 208. ... Neo4j is 2.1.0-M01 Community. Also I found an interesting issue with regard to utf8 usage. Say I have nodes which contain Ukrainian names, name_ua: "Євген" name_ua: "Ігор" (first letter is Ukrainian capital "і") name_ua: "Їжак" etc. I know that they *are* in the database. But as soon as I try to pass string with those Ukrainian letters to a query as a parameter, MATCH оn this string fails. $string = "Ірина"; $qry_name_lookup = "MATCH (n:FirstName {name_ua: {name_ua_val} }) RETURN n"; $name_lookup_qry = REST::Neo4p::Query->new($qry_name_lookup); $numrows = $name_lookup_qry->execute( 'name_ua_val' => $string ); returns zero rows, but works Ok for cyrillic names without Ukrainian characters. I'm puzzled. Thanks a lot for your attention! WBR, Andrii p.s. Those "given is experimental" and "when is experimental" warnings are somewhat boring, though harmless; don't you think it would be nice to have them hidden by default? Thanks!
Hi Andrii - I still have to work on the utf-8 issues, but the warnings should be gone with the new 0.2251 -- thanks MAJ On Tue May 13 03:41:42 2014, stesin@gmail.com wrote: Show quoted text
> Dear Mark, > thank you for issueing new release! > Unfortunately, it fails to build for me, here is relevant piece of the > console log: > ... > when is experimental at D:\Perl\cpan\build\REST-Neo4p-0.2250- > oQNdFU\blib\lib/REST/Neo4p/Query.pm line 378. > t\006_query.t ............... 20/? # rt80343 > [Conflict (409) thrown when fail is specified for create_unique on > indexes]END failed--call queue aborted. > # Looks like your test exited with 255 just after 47. > t\006_query.t ............... Dubious, test returned 255 (wstat 65280, > 0xff00) > All 47 subtests passed > t\007_accessors.t ........... given is experimental at > D:\Perl\cpan\build\REST-Neo4p-0.2250- > oQNdFU\blib\lib/REST/Neo4p/Agent.pm line 207. > when is experimental at D:\Perl\cpan\build\REST-Neo4p-0.2250- > oQNdFU\blib\lib/REST/Neo4p/Agent.pm line 208. > ... > > Neo4j is 2.1.0-M01 Community. > > Also I found an interesting issue with regard to utf8 usage. Say I > have nodes which contain Ukrainian names, > name_ua: "Євген" > name_ua: "Ігор" (first letter is Ukrainian capital "і") > name_ua: "Їжак" etc. > I know that they *are* in the database. But as soon as I try to pass > string with those Ukrainian letters to a query as a parameter, MATCH > оn this string fails. > $string = "Ірина"; > $qry_name_lookup = "MATCH (n:FirstName {name_ua: {name_ua_val} }) > RETURN n"; > $name_lookup_qry = REST::Neo4p::Query->new($qry_name_lookup); > $numrows = $name_lookup_qry->execute( 'name_ua_val' => $string ); > returns zero rows, but works Ok for cyrillic names without Ukrainian > characters. I'm puzzled. > > Thanks a lot for your attention! > WBR, > Andrii > > p.s. Those "given is experimental" and "when is experimental" warnings > are somewhat boring, though harmless; don't you think it would be nice > to have them hidden by default? Thanks!