They guys could create at least one in Malmö? Isn't Andreas there as well, and
certainly some more fine folks?
We can do one locally here in Gemany, perhaps Berlin (perhaps we can combine
that with our monthly flight to CPH).
Cheers
Michael
Am 14.03.2011 um 11:50 schrieb Jim Webber:
Hey
Berlin sounds great.
Last year a couple of guys met up at StudiVZ, and suddenly we were 30
people. Go for it, there is a LOT of good vibe in Beerlin!
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn
That would be great!
Or Frankfurt? It's a little more central (but Berlin is ok for me, too)
BTW: We should change the subject (it sounds so negative) ;-)
Since I created the original post, I'll start a new thread.
On 14.03.2011 13:02, Peter Neubauer wrote:
Berlin sounds great.
Last year a
: Thursday, March 10, 2011 2:21 AM
To: Neo4j user discussions
Subject: Re: [Neo4j] Issue with lucene index
2011/3/9 Rick Bullotta rick.bullo...@burningskysoftware.com
Hi, Mattias.
Is the ability to delete a node from a Lucene fulltext index the old way
(just provide node + key name) in M03
Hi Rick,
That prompts two more questions: Any chance of backporting this to Neo4J
1.2? If not, any rough estimate of the 1.3 release timetable?
Full releases are every quarter, M05 is due next week, and the following
release will be 1.3 GA. So you're looking at about 3 weeks.
Jim
PM
To: Neo4j user discussions
Subject: Re: [Neo4j] Issue with lucene index
Hi Rick,
That prompts two more questions: Any chance of backporting this to Neo4J
1.2? If not, any rough estimate of the 1.3 release timetable?
Full releases are every quarter, M05 is due next week, and the following
On Wed, Mar 9, 2011 at 8:24 PM, Mattias Persson
matt...@neotechnology.com wrote:
Correct, and go with the M03 milestone first because M04 will
introduce changes which requires an upgrade from a cleanly shut down
database.
Not so gentle from yours to force an upgrade from M03 to M04 sir...
;-)
2011/3/10 Massimo Lusetti mluse...@gmail.com
On Wed, Mar 9, 2011 at 8:24 PM, Mattias Persson
matt...@neotechnology.com wrote:
Correct, and go with the M03 milestone first because M04 will
introduce changes which requires an upgrade from a cleanly shut down
database.
Not so gentle from
Alex,
That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to
the latest milestone, you will no longer get this exception. Also, the
latest milestone will recover the store to a clean state. Your data will be
safe.
David
On Wed, Mar 9, 2011 at 10:26 AM, Axel Morgner
Den onsdagen den 9:e mars 2011 skrev David
Montagdavid.mon...@neotechnology.com:
Alex,
That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to
the latest milestone, you will no longer get this exception. Also, the
latest milestone will recover the store to a clean state.
Upgraded to 1.3.M03, issue is gone.
Thanks a lot!
Axel
Am 09.03.2011 20:24, schrieb Mattias Persson:
Den onsdagen den 9:e mars 2011 skrev David
Montagdavid.mon...@neotechnology.com:
Alex,
That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to
the latest milestone,
, March 09, 2011 2:24 PM
To: Neo4j user discussions
Subject: Re: [Neo4j] Issue with lucene index
Den onsdagen den 9:e mars 2011 skrev David
Montagdavid.mon...@neotechnology.com:
Alex,
That is caused by a bug. The bug has been fixed after 1.2. If you upgrade to
the latest milestone, you
...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org]
On Behalf Of Mattias Persson
Sent: Wednesday, March 09, 2011 2:24 PM
To: Neo4j user discussions
Subject: Re: [Neo4j] Issue with lucene index
Den onsdagen den 9:e mars 2011 skrev David
Montagdavid.mon...@neotechnology.com:
Alex
13 matches
Mail list logo
