this works in the console:
match n
where n.name =~ '^[A-Z ]+\\. [A-Z ]+'
return n;
On Monday, September 22, 2014 6:08:23 PM UTC-4, Michael Hunger wrote:
>
> You probably have to double escape.
>
> try:
>
> RETURN "A Z. A Z" =~ '^[A-Z ]+\\. [A-Z ]+'
>
> and in regexps you don't have to escape sp
You probably have to double escape.
try:
RETURN "A Z. A Z" =~ '^[A-Z ]+\\. [A-Z ]+'
and in regexps you don't have to escape spaces.
On Mon, Sep 22, 2014 at 11:07 PM, David Bigelow <
davidhbige...@simplifiedlogic.com> wrote:
> stumped by neo4j's regexp matching... It seems like glorified strin
stumped by neo4j's regexp matching... It seems like glorified string
matching (simple cases)
what if you want to use something like this?!
match n where n.name =~ '^[A-Z\ ]+\.\ [A-Z\ ]+' return n.name;
neo4j can't figure out what this is... everything should be escaped
properly -- but I think
Thanks - will check it out...
On Friday, September 19, 2014 4:28:00 PM UTC-4, Michael Hunger wrote:
>
> sorry, missed your email
> the regexp must be _the_ param
>
> var query_PATHS = "match n where n.name =~ {*myParam*} return n"
> var params = {myParam: "'.*"+text+".*'}
> ...
>
> On Fri, Sep
Yep, could you please do that? Thanks a lot.
On Mon, Sep 22, 2014 at 4:51 PM, Dmitrii Kosarev
wrote:
> It should be reported as a new issue, doesn't it?
>
>
> On Sunday, September 21, 2014 12:26:45 AM UTC+4, Michael Hunger wrote:
>>
>> Hi Dmitrii,
>>
>> I think you found an unfortunate issue, in
Hi Rita,
The reason we need multiple layers is that the layer object contains the
knowledge of what properties are used to store the location/type/bbox. To
store multiple locations on the same node requires different properties,
and therefor different layers.
The pom you referenced is very old an
It should be reported as a new issue, doesn't it?
On Sunday, September 21, 2014 12:26:45 AM UTC+4, Michael Hunger wrote:
>
> Hi Dmitrii,
>
> I think you found an unfortunate issue, in the internals all options for
> legacy indexes are strings, so you must use:
> "to_lower_case":"true"
>
> if you
Alright I splitted it now as I said.
The first part of simply inserting the Titles is like the Appln's I already
have in there.
So with
USING PERIODIC COMMIT 4000
LOAD CSV WITH HEADERS FROM "file:///C:/data/tls202_part01.txt" AS csvLine
WITH csvLine LIMIT 1000
MATCH (appln:Appln {ID: csvLine.a
Alright now testing with new version and splitted Title. Thanks.
Am Montag, 22. September 2014 12:16:24 UTC+2 schrieb Michael Hunger:
>
> *sigh*, this should work:
> http://neo4j.com/artifact.php?name=neo4j-community-2.1.4-windows.zip
>
> On Mon, Sep 22, 2014 at 11:58 AM, 'Curtis Mosters' via Neo
*sigh*, this should work:
http://neo4j.com/artifact.php?name=neo4j-community-2.1.4-windows.zip
On Mon, Sep 22, 2014 at 11:58 AM, 'Curtis Mosters' via Neo4j <
neo4j@googlegroups.com> wrote:
> Yeah that site seems new. And there is nowhere the *Older Version* thing.
>
> I think the updater just for
Yeah that site seems new. And there is nowhere the *Older Version* thing.
I think the updater just forget that section...
Or can you give me the direct download link for the latest binary zip
please?
Am Montag, 22. September 2014 08:22:36 UTC+2 schrieb Michael Hunger:
>
> Can you check neo4j.co
Hi Craig,
many thanks for you time and the implementation!
I see that the multiple points are supported in different layer, right? So
if I have 3 points on same node, I have to query on 3 different layers. I
have to verified the impact on performance for loading 3 layers.
Could you tell me how I
I test that I use one neo4j, the exception already exists.The follow is my
code:
@NodeEntity
public class Tcard implements Serializable{
private static final long serialVersionUID = -1466607516712774206L;
@GraphId
private Long tcardId;
@RelatedToVia(type = "TCARD_PRAISE", elementClass = TcardP
13 matches
Mail list logo
