I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j
Ruby gems.
This release contains a new gem, the neo4j-cypher gem which also can
be used from the neography and none JRuby platforms.
I've also released the jars for the new Neo4j 1.8 (neo4j-community,
neo4j-advanced and neo4j-enterprise).
One cool thing with the 2.2.0 release is that if you don't declare a
lucene index it will try to find it using cypher instead.
jruby-1.7.0.RC1 :002 > require 'neo4j'
=> true
jruby-1.7.0.RC1 :003 > class Person < Neo4j::Rails::Model
jruby-1.7.0.RC1 :004?> property :name, :default => '' # Notice, no
lucene index !!
jruby-1.7.0.RC1 :005?> end
=> [:name]
jruby-1.7.0.RC1 :006 > Person.create(:name => 'andreas')
I, [2012-10-04T09:41:53.710000 #1750] INFO -- : Starting local Neo4j ...
ruby-1.7.0.RC1 :008 > Person.find(:name => 'andreas')
=> #<Person:0xd8b9fac ...
CHANGELOGS
===========
Changelog for ruby neo4j gem:
== 2.2.0 / 2012-10-02
* Fix of neo4j-core configuration issue using boolean values #218
* Fixed RSpec issue on JRuby 1.7.x #217
* Aliased has_many to has_n, #183
== 2.2.0.rc1 / 2012-09-21
* Use the neo4j-cypher gem
* Better support for Orm Adapter, #212
* Use Cypher query when finder method does not have a lucene index, #210
Changelog for neo4j-core:
== 2.2.0 / 2012-10-02
* Use 1.0.0 of neo4j-cypher
* Fix of Neo4j::Config issue using boolean values, andreasronge/neo4j#218
* The []= operator checks that the value is a valid Neo4j value #16
== 2.2.0.rc1 / 2012-09-21
* Deleted, refactored, improved and moved cypher stuff to neo4j-cypher gem
* Add neo4j statistics, #15
On Thu, Oct 4, 2012 at 10:57 AM, Andreas Ronge <andreas.ro...@gmail.com> wrote:
> Hi
> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j
> Ruby gems.
> This release contains a new gem, the neo4j-cypher gem which also can
> be used from the neography and none JRuby platforms.
> I've also released the jars for the new Neo4j 1.8 (neo4j-community,
> neo4j-advanced and neo4j-enterprise).
> One cool thing with the 2.2.0 release is that if you don't declare a
> lucene index it will try to find it using cypher instead.
> jruby-1.7.0.RC1 :002 > require 'neo4j'
> => true
> jruby-1.7.0.RC1 :003 > class Person < Neo4j::Rails::Model
> jruby-1.7.0.RC1 :004?> property :name, :default => '' # Notice, no
> lucene index !!
> jruby-1.7.0.RC1 :005?> end
> => [:name]
> jruby-1.7.0.RC1 :006 > Person.create(:name => 'andreas')
> I, [2012-10-04T09:41:53.710000 #1750] INFO -- : Starting local Neo4j ...
> ruby-1.7.0.RC1 :008 > Person.find(:name => 'andreas')
> => #<Person:0xd8b9fac ...
> CHANGELOGS
> ===========
> Changelog for ruby neo4j gem:
> == 2.2.0 / 2012-10-02
> * Fix of neo4j-core configuration issue using boolean values #218
> * Fixed RSpec issue on JRuby 1.7.x #217
> * Aliased has_many to has_n, #183
> == 2.2.0.rc1 / 2012-09-21
> * Use the neo4j-cypher gem
> * Better support for Orm Adapter, #212
> * Use Cypher query when finder method does not have a lucene index, #210
> Changelog for neo4j-core:
> == 2.2.0 / 2012-10-02
> * Use 1.0.0 of neo4j-cypher
> * Fix of Neo4j::Config issue using boolean values, andreasronge/neo4j#218
> * The []= operator checks that the value is a valid Neo4j value #16
> == 2.2.0.rc1 / 2012-09-21
> * Deleted, refactored, improved and moved cypher stuff to neo4j-cypher gem
> * Add neo4j statistics, #15
On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
> Hi
> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j > Ruby gems. > This release contains a new gem, the neo4j-cypher gem which also can > be used from the neography and none JRuby platforms. > I've also released the jars for the new Neo4j 1.8 (neo4j-community, > neo4j-advanced and neo4j-enterprise).
> One cool thing with the 2.2.0 release is that if you don't declare a > lucene index it will try to find it using cypher instead.
> jruby-1.7.0.RC1 :002 > require 'neo4j' > => true > jruby-1.7.0.RC1 :003 > class Person < Neo4j::Rails::Model > jruby-1.7.0.RC1 :004?> property :name, :default => '' # Notice, no > lucene index !! > jruby-1.7.0.RC1 :005?> end > => [:name] > jruby-1.7.0.RC1 :006 > Person.create(:name => 'andreas') > I, [2012-10-04T09:41:53.710000 #1750] INFO -- : Starting local Neo4j ... > ruby-1.7.0.RC1 :008 > Person.find(:name => 'andreas') > => #<Person:0xd8b9fac ...
> CHANGELOGS > ===========
> Changelog for ruby neo4j gem:
> == 2.2.0 / 2012-10-02 > * Fix of neo4j-core configuration issue using boolean values #218 > * Fixed RSpec issue on JRuby 1.7.x #217 > * Aliased has_many to has_n, #183
> == 2.2.0.rc1 / 2012-09-21 > * Use the neo4j-cypher gem > * Better support for Orm Adapter, #212 > * Use Cypher query when finder method does not have a lucene index, #210
> Changelog for neo4j-core:
> == 2.2.0 / 2012-10-02 > * Use 1.0.0 of neo4j-cypher > * Fix of Neo4j::Config issue using boolean values, andreasronge/neo4j#218 > * The []= operator checks that the value is a valid Neo4j value #16
> == 2.2.0.rc1 / 2012-09-21 > * Deleted, refactored, improved and moved cypher stuff to neo4j-cypher gem > * Add neo4j statistics, #15
I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and other versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError: uninitialized constant Devise::Schema
> >> rails s > NameError: uninitialized constant Devise::Schema
> Thanks, > burak
> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>> Hi
>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j >> Ruby gems. >> This release contains a new gem, the neo4j-cypher gem which also can >> be used from the neography and none JRuby platforms. >> I've also released the jars for the new Neo4j 1.8 (neo4j-community, >> neo4j-advanced and neo4j-enterprise).
>> One cool thing with the 2.2.0 release is that if you don't declare a >> lucene index it will try to find it using cypher instead.
>> jruby-1.7.0.RC1 :002 > require 'neo4j' >> => true >> jruby-1.7.0.RC1 :003 > class Person < Neo4j::Rails::Model >> jruby-1.7.0.RC1 :004?> property :name, :default => '' # Notice, no >> lucene index !! >> jruby-1.7.0.RC1 :005?> end >> => [:name] >> jruby-1.7.0.RC1 :006 > Person.create(:name => 'andreas') >> I, [2012-10-04T09:41:53.710000 #1750] INFO -- : Starting local Neo4j ... >> ruby-1.7.0.RC1 :008 > Person.find(:name => 'andreas') >> => #<Person:0xd8b9fac ...
>> CHANGELOGS >> ===========
>> Changelog for ruby neo4j gem:
>> == 2.2.0 / 2012-10-02 >> * Fix of neo4j-core configuration issue using boolean values #218 >> * Fixed RSpec issue on JRuby 1.7.x #217 >> * Aliased has_many to has_n, #183
>> == 2.2.0.rc1 / 2012-09-21 >> * Use the neo4j-cypher gem >> * Better support for Orm Adapter, #212 >> * Use Cypher query when finder method does not have a lucene index, #210
>> Changelog for neo4j-core:
>> == 2.2.0 / 2012-10-02 >> * Use 1.0.0 of neo4j-cypher >> * Fix of Neo4j::Config issue using boolean values, andreasronge/neo4j#218 >> * The []= operator checks that the value is a valid Neo4j value #16
>> == 2.2.0.rc1 / 2012-09-21 >> * Deleted, refactored, improved and moved cypher stuff to neo4j-cypher >> gem >> * Add neo4j statistics, #15
On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and other > versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError: > uninitialized constant Devise::Schema
>> >> rails s >> NameError: uninitialized constant Devise::Schema
>> Thanks, >> burak
>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>> Hi
>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j >>> Ruby gems. >>> This release contains a new gem, the neo4j-cypher gem which also can >>> be used from the neography and none JRuby platforms. >>> I've also released the jars for the new Neo4j 1.8 (neo4j-community, >>> neo4j-advanced and neo4j-enterprise).
>>> One cool thing with the 2.2.0 release is that if you don't declare a >>> lucene index it will try to find it using cypher instead.
>>> jruby-1.7.0.RC1 :002 > require 'neo4j' >>> => true >>> jruby-1.7.0.RC1 :003 > class Person < Neo4j::Rails::Model >>> jruby-1.7.0.RC1 :004?> property :name, :default => '' # Notice, no >>> lucene index !! >>> jruby-1.7.0.RC1 :005?> end >>> => [:name] >>> jruby-1.7.0.RC1 :006 > Person.create(:name => 'andreas') >>> I, [2012-10-04T09:41:53.710000 #1750] INFO -- : Starting local Neo4j >>> ... >>> ruby-1.7.0.RC1 :008 > Person.find(:name => 'andreas') >>> => #<Person:0xd8b9fac ...
>>> CHANGELOGS >>> ===========
>>> Changelog for ruby neo4j gem:
>>> == 2.2.0 / 2012-10-02 >>> * Fix of neo4j-core configuration issue using boolean values #218 >>> * Fixed RSpec issue on JRuby 1.7.x #217 >>> * Aliased has_many to has_n, #183
>>> == 2.2.0.rc1 / 2012-09-21 >>> * Use the neo4j-cypher gem >>> * Better support for Orm Adapter, #212 >>> * Use Cypher query when finder method does not have a lucene index, #210
>>> Changelog for neo4j-core:
>>> == 2.2.0 / 2012-10-02 >>> * Use 1.0.0 of neo4j-cypher >>> * Fix of Neo4j::Config issue using boolean values, >>> andreasronge/neo4j#218 >>> * The []= operator checks that the value is a valid Neo4j value #16
>>> == 2.2.0.rc1 / 2012-09-21 >>> * Deleted, refactored, improved and moved cypher stuff to neo4j-cypher >>> gem >>> * Add neo4j statistics, #15
On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio....@gmail.com> wrote:
> Guys,
> the devise-neo4j code was last modified on Sep 25, 2011, so don't expect it
> to work after so many changes happened in Neo4j.
> Regards,
> Antonio
> On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and other
>> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError:
>> uninitialized constant Devise::Schema
>>> >> rails s
>>> NameError: uninitialized constant Devise::Schema
>>> Thanks,
>>> burak
>>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>>> Hi
>>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j
>>>> Ruby gems.
>>>> This release contains a new gem, the neo4j-cypher gem which also can
>>>> be used from the neography and none JRuby platforms.
>>>> I've also released the jars for the new Neo4j 1.8 (neo4j-community,
>>>> neo4j-advanced and neo4j-enterprise).
>>>> One cool thing with the 2.2.0 release is that if you don't declare a
>>>> lucene index it will try to find it using cypher instead.
>>>> jruby-1.7.0.RC1 :002 > require 'neo4j'
>>>> => true
>>>> jruby-1.7.0.RC1 :003 > class Person < Neo4j::Rails::Model
>>>> jruby-1.7.0.RC1 :004?> property :name, :default => '' # Notice, no
>>>> lucene index !!
>>>> jruby-1.7.0.RC1 :005?> end
>>>> => [:name]
>>>> jruby-1.7.0.RC1 :006 > Person.create(:name => 'andreas')
>>>> I, [2012-10-04T09:41:53.710000 #1750] INFO -- : Starting local Neo4j
>>>> ...
>>>> ruby-1.7.0.RC1 :008 > Person.find(:name => 'andreas')
>>>> => #<Person:0xd8b9fac ...
>>>> CHANGELOGS
>>>> ===========
>>>> Changelog for ruby neo4j gem:
>>>> == 2.2.0 / 2012-10-02
>>>> * Fix of neo4j-core configuration issue using boolean values #218
>>>> * Fixed RSpec issue on JRuby 1.7.x #217
>>>> * Aliased has_many to has_n, #183
>>>> == 2.2.0.rc1 / 2012-09-21
>>>> * Use the neo4j-cypher gem
>>>> * Better support for Orm Adapter, #212
>>>> * Use Cypher query when finder method does not have a lucene index, #210
>>>> Changelog for neo4j-core:
>>>> == 2.2.0 / 2012-10-02
>>>> * Use 1.0.0 of neo4j-cypher
>>>> * Fix of Neo4j::Config issue using boolean values,
>>>> andreasronge/neo4j#218
>>>> * The []= operator checks that the value is a valid Neo4j value #16
>>>> == 2.2.0.rc1 / 2012-09-21
>>>> * Deleted, refactored, improved and moved cypher stuff to neo4j-cypher
>>>> gem
>>>> * Add neo4j statistics, #15
> To post to this group, send email to neo4jrb@googlegroups.com.
> To unsubscribe from this group, send email to
> neo4jrb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/neo4jrb?hl=en.
I have a folk of these at https://github.com/cfitz/devise-neo4j that I am
using which should work with both the new version of neo4jrb and devise
2.0.4. However, I haven't added any tests to the gem since I am testing
this in the application....maybe in a couple of days I'll add the tests and
put in a proper pull request....let me know if you have any questions...
On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andreas.ro...@gmail.com>wrote:
> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio....@gmail.com> wrote:
> > Guys,
> > the devise-neo4j code was last modified on Sep 25, 2011, so don't expect
> it
> > to work after so many changes happened in Neo4j.
> > Regards,
> > Antonio
> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and other
> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError:
> >> uninitialized constant Devise::Schema
> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
> >>>> Hi
> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the neo4j
> >>>> Ruby gems.
> >>>> This release contains a new gem, the neo4j-cypher gem which also can
> >>>> be used from the neography and none JRuby platforms.
> >>>> I've also released the jars for the new Neo4j 1.8 (neo4j-community,
> >>>> neo4j-advanced and neo4j-enterprise).
> >>>> == 2.2.0 / 2012-10-02
> >>>> * Fix of neo4j-core configuration issue using boolean values #218
> >>>> * Fixed RSpec issue on JRuby 1.7.x #217
> >>>> * Aliased has_many to has_n, #183
> >>>> == 2.2.0.rc1 / 2012-09-21
> >>>> * Use the neo4j-cypher gem
> >>>> * Better support for Orm Adapter, #212
> >>>> * Use Cypher query when finder method does not have a lucene index,
> #210
> >>>> Changelog for neo4j-core:
> >>>> == 2.2.0 / 2012-10-02
> >>>> * Use 1.0.0 of neo4j-cypher
> >>>> * Fix of Neo4j::Config issue using boolean values,
> >>>> andreasronge/neo4j#218
> >>>> * The []= operator checks that the value is a valid Neo4j value #16
> >>>> == 2.2.0.rc1 / 2012-09-21
> >>>> * Deleted, refactored, improved and moved cypher stuff to neo4j-cypher
> >>>> gem
> >>>> * Add neo4j statistics, #15
> > To post to this group, send email to neo4jrb@googlegroups.com.
> > To unsubscribe from this group, send email to
> > neo4jrb+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/neo4jrb?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "neo4jrb" group.
> To post to this group, send email to neo4jrb@googlegroups.com.
> To unsubscribe from this group, send email to
> neo4jrb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/neo4jrb?hl=en.
On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
> I have a folk of these at https://github.com/cfitz/devise-neo4j that I am > using which should work with both the new version of neo4jrb and devise > 2.0.4. However, I haven't added any tests to the gem since I am testing > this in the application....maybe in a couple of days I'll add the tests and > put in a proper pull request....let me know if you have any questions...
> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com<javascript:> > > wrote:
>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com <javascript:>> >> wrote: >> > Guys,
>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't >> expect it >> > to work after so many changes happened in Neo4j.
>> > Regards, >> > Antonio
>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and other >> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError: >> >> uninitialized constant Devise::Schema
>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>> >>>> Hi
>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the >> neo4j >> >>>> Ruby gems. >> >>>> This release contains a new gem, the neo4j-cypher gem which also can >> >>>> be used from the neography and none JRuby platforms. >> >>>> I've also released the jars for the new Neo4j 1.8 (neo4j-community, >> >>>> neo4j-advanced and neo4j-enterprise).
>> >>>> == 2.2.0 / 2012-10-02 >> >>>> * Fix of neo4j-core configuration issue using boolean values #218 >> >>>> * Fixed RSpec issue on JRuby 1.7.x #217 >> >>>> * Aliased has_many to has_n, #183
>> >>>> == 2.2.0.rc1 / 2012-09-21 >> >>>> * Use the neo4j-cypher gem >> >>>> * Better support for Orm Adapter, #212 >> >>>> * Use Cypher query when finder method does not have a lucene index, >> #210
>> >>>> Changelog for neo4j-core:
>> >>>> == 2.2.0 / 2012-10-02 >> >>>> * Use 1.0.0 of neo4j-cypher >> >>>> * Fix of Neo4j::Config issue using boolean values, >> >>>> andreasronge/neo4j#218 >> >>>> * The []= operator checks that the value is a valid Neo4j value #16
>> >>>> == 2.2.0.rc1 / 2012-09-21 >> >>>> * Deleted, refactored, improved and moved cypher stuff to >> neo4j-cypher >> >>>> gem >> >>>> * Add neo4j statistics, #15
>> >>>> For more info, check the github issues.
>> >>>> Cheers >> >>>> Andreas
>> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "neo4jrb" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/neo4jrb/-/u8f1lfm70ZIJ.
>> > To post to this group, send email to neo...@googlegroups.com<javascript:> >> . >> > To unsubscribe from this group, send email to >> > neo4jrb+u...@googlegroups.com <javascript:>. >> > For more options, visit this group at >> > http://groups.google.com/group/neo4jrb?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "neo4jrb" group. >> To post to this group, send email to neo...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> neo4jrb+u...@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/neo4jrb?hl=en.
> neo4j (= 2.0.0) java depends on
> orm_adapter (0.4.0)
> burak
> On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>> I have a folk of these at https://github.com/cfitz/**devise-neo4j<https://github.com/cfitz/devise-neo4j>that I am using which should work with both the new version of neo4jrb and
>> devise 2.0.4. However, I haven't added any tests to the gem since I am
>> testing this in the application....maybe in a couple of days I'll add the
>> tests and put in a proper pull request....let me know if you have any
>> questions...
>> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com>wrote:
>>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
>>> > Guys,
>>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
>>> expect it
>>> > to work after so many changes happened in Neo4j.
>>> > Regards,
>>> > Antonio
>>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and
>>> other
>>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError:
>>> >> uninitialized constant Devise::Schema
>>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>> >>>> Hi
>>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the
>>> neo4j
>>> >>>> Ruby gems.
>>> >>>> This release contains a new gem, the neo4j-cypher gem which also can
>>> >>>> be used from the neography and none JRuby platforms.
>>> >>>> I've also released the jars for the new Neo4j 1.8 (neo4j-community,
>>> >>>> neo4j-advanced and neo4j-enterprise).
>>> >>>> == 2.2.0 / 2012-10-02
>>> >>>> * Fix of neo4j-core configuration issue using boolean values #218
>>> >>>> * Fixed RSpec issue on JRuby 1.7.x #217
>>> >>>> * Aliased has_many to has_n, #183
>>> >>>> == 2.2.0.rc1 / 2012-09-21
>>> >>>> * Use the neo4j-cypher gem
>>> >>>> * Better support for Orm Adapter, #212
>>> >>>> * Use Cypher query when finder method does not have a lucene index,
>>> #210
>>> >>>> Changelog for neo4j-core:
>>> >>>> == 2.2.0 / 2012-10-02
>>> >>>> * Use 1.0.0 of neo4j-cypher
>>> >>>> * Fix of Neo4j::Config issue using boolean values,
>>> >>>> andreasronge/neo4j#218
>>> >>>> * The []= operator checks that the value is a valid Neo4j value #16
>>> >>>> == 2.2.0.rc1 / 2012-09-21
>>> >>>> * Deleted, refactored, improved and moved cypher stuff to
>>> neo4j-cypher
>>> >>>> gem
>>> >>>> * Add neo4j statistics, #15
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "neo4jrb" group.
>>> To post to this group, send email to neo...@googlegroups.com.
>>> To unsubscribe from this group, send email to neo4jrb+u...@**
>>> googlegroups.com.
> To post to this group, send email to neo4jrb@googlegroups.com.
> To unsubscribe from this group, send email to
> neo4jrb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/neo4jrb?hl=en.
> neo4j (= 2.0.0) java depends on
> orm_adapter (0.4.0)
> burak
> On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>> I have a folk of these at https://github.com/cfitz/devise-neo4j that I am
>> using which should work with both the new version of neo4jrb and devise
>> 2.0.4. However, I haven't added any tests to the gem since I am testing
>> this in the application....maybe in a couple of days I'll add the tests and
>> put in a proper pull request....let me know if you have any questions...
>> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com>
>> wrote:
>>> Hi
>>> I think it should work on the old devise < version 2.0.
>>> Btw, according to this
>>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
>>> > Guys,
>>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
>>> > expect it
>>> > to work after so many changes happened in Neo4j.
>>> > Regards,
>>> > Antonio
>>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and
>>> >> other
>>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError:
>>> >> uninitialized constant Devise::Schema
>>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>> >>>> Hi
>>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the
>>> >>>> neo4j
>>> >>>> Ruby gems.
>>> >>>> This release contains a new gem, the neo4j-cypher gem which also can
>>> >>>> be used from the neography and none JRuby platforms.
>>> >>>> I've also released the jars for the new Neo4j 1.8 (neo4j-community,
>>> >>>> neo4j-advanced and neo4j-enterprise).
>>> >>>> == 2.2.0 / 2012-10-02
>>> >>>> * Fix of neo4j-core configuration issue using boolean values #218
>>> >>>> * Fixed RSpec issue on JRuby 1.7.x #217
>>> >>>> * Aliased has_many to has_n, #183
>>> >>>> == 2.2.0.rc1 / 2012-09-21
>>> >>>> * Use the neo4j-cypher gem
>>> >>>> * Better support for Orm Adapter, #212
>>> >>>> * Use Cypher query when finder method does not have a lucene index,
>>> >>>> #210
>>> >>>> Changelog for neo4j-core:
>>> >>>> == 2.2.0 / 2012-10-02
>>> >>>> * Use 1.0.0 of neo4j-cypher
>>> >>>> * Fix of Neo4j::Config issue using boolean values,
>>> >>>> andreasronge/neo4j#218
>>> >>>> * The []= operator checks that the value is a valid Neo4j value #16
>>> >>>> == 2.2.0.rc1 / 2012-09-21
>>> >>>> * Deleted, refactored, improved and moved cypher stuff to
>>> >>>> neo4j-cypher
>>> >>>> gem
>>> >>>> * Add neo4j statistics, #15
>>> >>>> For more info, check the github issues.
>>> >>>> Cheers
>>> >>>> Andreas
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "neo4jrb" group.
>>> > To view this discussion on the web visit
>>> > https://groups.google.com/d/msg/neo4jrb/-/u8f1lfm70ZIJ.
>>> > To post to this group, send email to neo...@googlegroups.com.
>>> > To unsubscribe from this group, send email to
>>> > neo4jrb+u...@googlegroups.com.
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "neo4jrb" group.
>>> To post to this group, send email to neo...@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> neo4jrb+u...@googlegroups.com.
> To post to this group, send email to neo4jrb@googlegroups.com.
> To unsubscribe from this group, send email to
> neo4jrb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/neo4jrb?hl=en.
Ah, yeah, that would make sense....I removed the .lock file from github.
Let me know if that fixes the issue.
I am thinking I ought to update this so it works with the newer version of
devise and update the tests. I don't have time today, but I'll try to
squeeze it in tomorrow...
On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andreas.ro...@gmail.com>wrote:
> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
> >> I have a folk of these at https://github.com/cfitz/devise-neo4j that I
> am
> >> using which should work with both the new version of neo4jrb and devise
> >> 2.0.4. However, I haven't added any tests to the gem since I am testing
> >> this in the application....maybe in a couple of days I'll add the tests
> and
> >> put in a proper pull request....let me know if you have any questions...
> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com>
> >> wrote:
> >>> Hi
> >>> I think it should work on the old devise < version 2.0.
> >>> Btw, according to this
> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
> >>> > Guys,
> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
> >>> > expect it
> >>> > to work after so many changes happened in Neo4j.
> >>> > Regards,
> >>> > Antonio
> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and
> >>> >> other
> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError:
> >>> >> uninitialized constant Devise::Schema
> >>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
> >>> >>>> Hi
> >>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the
> >>> >>>> neo4j
> >>> >>>> Ruby gems.
> >>> >>>> This release contains a new gem, the neo4j-cypher gem which also
> can
> >>> >>>> be used from the neography and none JRuby platforms.
> >>> >>>> I've also released the jars for the new Neo4j 1.8
> (neo4j-community,
> >>> >>>> neo4j-advanced and neo4j-enterprise).
> >>> >>>> == 2.2.0 / 2012-10-02
> >>> >>>> * Fix of neo4j-core configuration issue using boolean values #218
> >>> >>>> * Fixed RSpec issue on JRuby 1.7.x #217
> >>> >>>> * Aliased has_many to has_n, #183
> >>> >>>> == 2.2.0.rc1 / 2012-09-21
> >>> >>>> * Use the neo4j-cypher gem
> >>> >>>> * Better support for Orm Adapter, #212
> >>> >>>> * Use Cypher query when finder method does not have a lucene
> index,
> >>> >>>> #210
> >>> >>>> Changelog for neo4j-core:
> >>> >>>> == 2.2.0 / 2012-10-02
> >>> >>>> * Use 1.0.0 of neo4j-cypher
> >>> >>>> * Fix of Neo4j::Config issue using boolean values,
> >>> >>>> andreasronge/neo4j#218
> >>> >>>> * The []= operator checks that the value is a valid Neo4j value
> #16
> >>> >>>> For more info, check the github issues.
> >>> >>>> Cheers
> >>> >>>> Andreas
> >>> > --
> >>> > You received this message because you are subscribed to the Google
> >>> > Groups
> >>> > "neo4jrb" group.
> >>> > To view this discussion on the web visit
> >>> > https://groups.google.com/d/msg/neo4jrb/-/u8f1lfm70ZIJ.
> >>> > To post to this group, send email to neo...@googlegroups.com.
> >>> > To unsubscribe from this group, send email to
> >>> > neo4jrb+u...@googlegroups.com.
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "neo4jrb" group.
> >>> To post to this group, send email to neo...@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> neo4jrb+u...@googlegroups.com.
> > To post to this group, send email to neo4jrb@googlegroups.com.
> > To unsubscribe from this group, send email to
> > neo4jrb+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/neo4jrb?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "neo4jrb" group.
> To post to this group, send email to neo4jrb@googlegroups.com.
> To unsubscribe from this group, send email to
> neo4jrb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/neo4jrb?hl=en.
> Ah, yeah, that would make sense....I removed the .lock file from github.
> Let me know if that fixes the issue.
> I am thinking I ought to update this so it works with the newer version of
> devise and update the tests. I don't have time today, but I'll try to
> squeeze it in tomorrow...
> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andreas.ro...@gmail.com>wrote:
>> Looks like the Gemfile.lock is in git. It should not be checked in
>> (should be in .gitignore)
>> See,
>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>> >> I have a folk of these at https://github.com/cfitz/devise-neo4j that
>> I am
>> >> using which should work with both the new version of neo4jrb and devise
>> >> 2.0.4. However, I haven't added any tests to the gem since I am
>> testing
>> >> this in the application....maybe in a couple of days I'll add the
>> tests and
>> >> put in a proper pull request....let me know if you have any
>> questions...
>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com>
>> >> wrote:
>> >>> Hi
>> >>> I think it should work on the old devise < version 2.0.
>> >>> Btw, according to this
>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
>> >>> > Guys,
>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
>> >>> > expect it
>> >>> > to work after so many changes happened in Neo4j.
>> >>> > Regards,
>> >>> > Antonio
>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and
>> >>> >> other
>> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError:
>> >>> >> uninitialized constant Devise::Schema
>> >>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>> >>> >>>> Hi
>> >>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the
>> >>> >>>> neo4j
>> >>> >>>> Ruby gems.
>> >>> >>>> This release contains a new gem, the neo4j-cypher gem which also
>> can
>> >>> >>>> be used from the neography and none JRuby platforms.
>> >>> >>>> I've also released the jars for the new Neo4j 1.8
>> (neo4j-community,
>> >>> >>>> neo4j-advanced and neo4j-enterprise).
>> >>> >>>> One cool thing with the 2.2.0 release is that if you don't
>> declare a
>> >>> >>>> lucene index it will try to find it using cypher instead.
>> >>> >>>> == 2.2.0 / 2012-10-02
>> >>> >>>> * Fix of neo4j-core configuration issue using boolean values #218
>> >>> >>>> * Fixed RSpec issue on JRuby 1.7.x #217
>> >>> >>>> * Aliased has_many to has_n, #183
>> >>> >>>> == 2.2.0.rc1 / 2012-09-21
>> >>> >>>> * Use the neo4j-cypher gem
>> >>> >>>> * Better support for Orm Adapter, #212
>> >>> >>>> * Use Cypher query when finder method does not have a lucene
>> index,
>> >>> >>>> #210
>> >>> >>>> Changelog for neo4j-core:
>> >>> >>>> == 2.2.0 / 2012-10-02
>> >>> >>>> * Use 1.0.0 of neo4j-cypher
>> >>> >>>> * Fix of Neo4j::Config issue using boolean values,
>> >>> >>>> andreasronge/neo4j#218
>> >>> >>>> * The []= operator checks that the value is a valid Neo4j value
>> #16
>> >>> >>>> For more info, check the github issues.
>> >>> >>>> Cheers
>> >>> >>>> Andreas
>> >>> > --
>> >>> > You received this message because you are subscribed to the Google
>> >>> > Groups
>> >>> > "neo4jrb" group.
>> >>> > To view this discussion on the web visit
>> >>> > https://groups.google.com/d/msg/neo4jrb/-/u8f1lfm70ZIJ.
>> >>> > To post to this group, send email to neo...@googlegroups.com.
>> >>> > To unsubscribe from this group, send email to
>> >>> > neo4jrb+u...@googlegroups.com.
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> Groups
>> >>> "neo4jrb" group.
>> >>> To post to this group, send email to neo...@googlegroups.com.
>> >>> To unsubscribe from this group, send email to
>> >>> neo4jrb+u...@googlegroups.com.
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "neo4jrb" group.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msg/neo4jrb/-/72hMXsEJU_gJ.
>> > To post to this group, send email to neo4jrb@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > neo4jrb+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/neo4jrb?hl=en.
>> --
>> You received this message because you are subscribed to the Google Groups
>> "neo4jrb" group.
>> To post to this group, send email to neo4jrb@googlegroups.com.
>> To unsubscribe from this group, send email to
>> neo4jrb+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/neo4jrb?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "neo4jrb" group.
> To post to this group, send email to neo4jrb@googlegroups.com.
> To unsubscribe from this group, send email to
> neo4jrb+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/neo4jrb?hl=en.
On Monday, November 5, 2012 3:08:57 PM UTC+2, Chris F. wrote:
> Ah, yeah, that would make sense....I removed the .lock file from github. > Let me know if that fixes the issue.
> I am thinking I ought to update this so it works with the newer version of > devise and update the tests. I don't have time today, but I'll try to > squeeze it in tomorrow...
> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andrea...@gmail.com<javascript:> > > wrote:
>> Looks like the Gemfile.lock is in git. It should not be checked in >> (should be in .gitignore) >> See,
>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>> >> I have a folk of these at https://github.com/cfitz/devise-neo4j that >> I am >> >> using which should work with both the new version of neo4jrb and devise >> >> 2.0.4. However, I haven't added any tests to the gem since I am >> testing >> >> this in the application....maybe in a couple of days I'll add the >> tests and >> >> put in a proper pull request....let me know if you have any >> questions...
>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com> >> >> wrote:
>> >>> Hi
>> >>> I think it should work on the old devise < version 2.0. >> >>> Btw, according to this
>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote: >> >>> > Guys,
>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't >> >>> > expect it >> >>> > to work after so many changes happened in Neo4j.
>> >>> > Regards, >> >>> > Antonio
>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and >> >>> >> other >> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same NameError: >> >>> >> uninitialized constant Devise::Schema
>> >>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>> >>> >>>> Hi
>> >>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the >> >>> >>>> neo4j >> >>> >>>> Ruby gems. >> >>> >>>> This release contains a new gem, the neo4j-cypher gem which also >> can >> >>> >>>> be used from the neography and none JRuby platforms. >> >>> >>>> I've also released the jars for the new Neo4j 1.8 >> (neo4j-community, >> >>> >>>> neo4j-advanced and neo4j-enterprise).
>> >>> >>>> One cool thing with the 2.2.0 release is that if you don't >> declare a >> >>> >>>> lucene index it will try to find it using cypher instead.
>> >>> >>>> == 2.2.0 / 2012-10-02 >> >>> >>>> * Fix of neo4j-core configuration issue using boolean values #218 >> >>> >>>> * Fixed RSpec issue on JRuby 1.7.x #217 >> >>> >>>> * Aliased has_many to has_n, #183
>> >>> >>>> == 2.2.0.rc1 / 2012-09-21 >> >>> >>>> * Use the neo4j-cypher gem >> >>> >>>> * Better support for Orm Adapter, #212 >> >>> >>>> * Use Cypher query when finder method does not have a lucene >> index, >> >>> >>>> #210
>> >>> >>>> Changelog for neo4j-core:
>> >>> >>>> == 2.2.0 / 2012-10-02 >> >>> >>>> * Use 1.0.0 of neo4j-cypher >> >>> >>>> * Fix of Neo4j::Config issue using boolean values, >> >>> >>>> andreasronge/neo4j#218 >> >>> >>>> * The []= operator checks that the value is a valid Neo4j value >> #16
>> >>> >>>> For more info, check the github issues.
>> >>> >>>> Cheers >> >>> >>>> Andreas
>> >>> > -- >> >>> > You received this message because you are subscribed to the Google >> >>> > Groups >> >>> > "neo4jrb" group. >> >>> > To view this discussion on the web visit >> >>> > https://groups.google.com/d/msg/neo4jrb/-/u8f1lfm70ZIJ.
>> >>> > To post to this group, send email to neo...@googlegroups.com.
>> >>> > To unsubscribe from this group, send email to >> >>> > neo4jrb+u...@googlegroups.com.
>> >>> -- >> >>> You received this message because you are subscribed to the Google >> Groups >> >>> "neo4jrb" group. >> >>> To post to this group, send email to neo...@googlegroups.com. >> >>> To unsubscribe from this group, send email to >> >>> neo4jrb+u...@googlegroups.com.
>> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "neo4jrb" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/neo4jrb/-/72hMXsEJU_gJ.
>> > To post to this group, send email to neo...@googlegroups.com<javascript:> >> . >> > To unsubscribe from this group, send email to >> > neo4jrb+u...@googlegroups.com <javascript:>. >> > For more options, visit this group at >> > http://groups.google.com/group/neo4jrb?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "neo4jrb" group. >> To post to this group, send email to neo...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> neo4jrb+u...@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/neo4jrb?hl=en.
Most of the tests pass, mostly minor problems. You can see them updates in
the test/overrides folder. There is a strange issue with one of the devise
tests that is checking password confirmation validation, but I cannot
replicate it (that is, password confirmation works fine for me in the app
and in console).
I'll try and look into this ... eventually.
you can try it out yourself:
gem install rails
rails new myapp -m http://andreasronge.github.com/neo4j/rails.rb -O
cd myapp
add to your Gem File :
gem 'devise-neo4j', :git => 'git://github.com/cfitz/devise-neo4j.git',
:branch => 'devise2'
bundle
rails generate devise:install --orm=neo4j
bundle exec rails g neo4j:devise User
add devise_for :users to config/routes.rb (not sure why generator is not
adding this...)
rails s
go to http://localhost:3000/users/sign_up, sign up, then go to
http://localhost:3000/users/ . Try and edit your password with a bad
confirmation....everything works as I'd expected it to.
Otherwise, let me know what you think or if anyone sees any suggestions for
improvement... b,chris.
On Mon, Nov 5, 2012 at 2:53 PM, arikan <ari...@gmail.com> wrote:
> Thanks a lot Chris, Andreas,
> Now devise-neo4j works fine, after the Gemfile.lock update, both
> with Rails 3.1.7 and Rails 3.2.8, and neo4j 2.0.0 and neo4j 2.2.0.
> Burak
> On Monday, November 5, 2012 3:08:57 PM UTC+2, Chris F. wrote:
>> Ah, yeah, that would make sense....I removed the .lock file from github.
>> Let me know if that fixes the issue.
>> I am thinking I ought to update this so it works with the newer version
>> of devise and update the tests. I don't have time today, but I'll try to
>> squeeze it in tomorrow...
>> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andrea...@gmail.com>wrote:
>>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>>> >> I have a folk of these at https://github.com/cfitz/**devise-neo4j<https://github.com/cfitz/devise-neo4j>that I am
>>> >> using which should work with both the new version of neo4jrb and
>>> devise
>>> >> 2.0.4. However, I haven't added any tests to the gem since I am
>>> testing
>>> >> this in the application....maybe in a couple of days I'll add the
>>> tests and
>>> >> put in a proper pull request....let me know if you have any
>>> questions...
>>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com>
>>> >> wrote:
>>> >>> Hi
>>> >>> I think it should work on the old devise < version 2.0.
>>> >>> Btw, according to this
>>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
>>> >>> > Guys,
>>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
>>> >>> > expect it
>>> >>> > to work after so many changes happened in Neo4j.
>>> >>> > Regards,
>>> >>> > Antonio
>>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and
>>> >>> >> other
>>> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same
>>> NameError:
>>> >>> >> uninitialized constant Devise::Schema
>>> >>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>> >>> >>>> Hi
>>> >>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and the
>>> >>> >>>> neo4j
>>> >>> >>>> Ruby gems.
>>> >>> >>>> This release contains a new gem, the neo4j-cypher gem which
>>> also can
>>> >>> >>>> be used from the neography and none JRuby platforms.
>>> >>> >>>> I've also released the jars for the new Neo4j 1.8
>>> (neo4j-community,
>>> >>> >>>> neo4j-advanced and neo4j-enterprise).
>>> >>> >>>> One cool thing with the 2.2.0 release is that if you don't
>>> declare a
>>> >>> >>>> lucene index it will try to find it using cypher instead.
>>> >>> >>>> == 2.2.0.rc1 / 2012-09-21
>>> >>> >>>> * Use the neo4j-cypher gem
>>> >>> >>>> * Better support for Orm Adapter, #212
>>> >>> >>>> * Use Cypher query when finder method does not have a lucene
>>> index,
>>> >>> >>>> #210
>>> >>> >>>> Changelog for neo4j-core:
>>> >>> >>>> == 2.2.0 / 2012-10-02
>>> >>> >>>> * Use 1.0.0 of neo4j-cypher
>>> >>> >>>> * Fix of Neo4j::Config issue using boolean values,
>>> >>> >>>> andreasronge/neo4j#218
>>> >>> >>>> * The []= operator checks that the value is a valid Neo4j value
>>> #16
>>> >>> --
>>> >>> You received this message because you are subscribed to the Google
>>> Groups
>>> >>> "neo4jrb" group.
>>> >>> To post to this group, send email to neo...@googlegroups.com.
>>> >>> To unsubscribe from this group, send
> Most of the tests pass, mostly minor problems. You can see them updates in
> the test/overrides folder. There is a strange issue with one of the devise
> tests that is checking password confirmation validation, but I cannot
> replicate it (that is, password confirmation works fine for me in the app
> and in console).
> I'll try and look into this ... eventually.
> you can try it out yourself:
> gem install rails
> rails new myapp -m http://andreasronge.github.com/neo4j/rails.rb -O
> cd myapp
> add to your Gem File :
> gem 'devise-neo4j', :git => 'git://github.com/cfitz/devise-neo4j.git',
> :branch => 'devise2'
> bundle
> rails generate devise:install --orm=neo4j
> bundle exec rails g neo4j:devise User
> add devise_for :users to config/routes.rb (not sure why generator is not
> adding this...)
> rails s
> go to http://localhost:3000/users/sign_up, sign up, then go to
> http://localhost:3000/users/ . Try and edit your password with a bad
> confirmation....everything works as I'd expected it to.
> Otherwise, let me know what you think or if anyone sees any suggestions
> for improvement... b,chris.
> On Mon, Nov 5, 2012 at 2:53 PM, arikan <ari...@gmail.com> wrote:
>> Thanks a lot Chris, Andreas,
>> Now devise-neo4j works fine, after the Gemfile.lock update, both
>> with Rails 3.1.7 and Rails 3.2.8, and neo4j 2.0.0 and neo4j 2.2.0.
>> Burak
>> On Monday, November 5, 2012 3:08:57 PM UTC+2, Chris F. wrote:
>>> Ah, yeah, that would make sense....I removed the .lock file from github.
>>> Let me know if that fixes the issue.
>>> I am thinking I ought to update this so it works with the newer version
>>> of devise and update the tests. I don't have time today, but I'll try to
>>> squeeze it in tomorrow...
>>> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andrea...@gmail.com>wrote:
>>>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>>>> >> I have a folk of these at https://github.com/cfitz/**devise-neo4j<https://github.com/cfitz/devise-neo4j>that I am
>>>> >> using which should work with both the new version of neo4jrb and
>>>> devise
>>>> >> 2.0.4. However, I haven't added any tests to the gem since I am
>>>> testing
>>>> >> this in the application....maybe in a couple of days I'll add the
>>>> tests and
>>>> >> put in a proper pull request....let me know if you have any
>>>> questions...
>>>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com>
>>>> >> wrote:
>>>> >>> Hi
>>>> >>> I think it should work on the old devise < version 2.0.
>>>> >>> Btw, according to this
>>>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
>>>> >>> > Guys,
>>>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
>>>> >>> > expect it
>>>> >>> > to work after so many changes happened in Neo4j.
>>>> >>> > Regards,
>>>> >>> > Antonio
>>>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and
>>>> >>> >> other
>>>> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same
>>>> NameError:
>>>> >>> >> uninitialized constant Devise::Schema
>>>> >>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>>> >>> >>>> Hi
>>>> >>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and
>>>> the
>>>> >>> >>>> neo4j
>>>> >>> >>>> Ruby gems.
>>>> >>> >>>> This release contains a new gem, the neo4j-cypher gem which
>>>> also can
>>>> >>> >>>> be used from the neography and none JRuby platforms.
>>>> >>> >>>> I've also released the jars for the new Neo4j 1.8
>>>> (neo4j-community,
>>>> >>> >>>> neo4j-advanced and neo4j-enterprise).
>>>> >>> >>>> One cool thing with the 2.2.0 release is that if you don't
>>>> declare a
>>>> >>> >>>> lucene index it will try to find it using cypher instead.
>>>> >>> >>>> == 2.2.0.rc1 / 2012-09-21
>>>> >>> >>>> * Use the neo4j-cypher gem
>>>> >>> >>>> * Better support for Orm Adapter, #212
>>>> >>> >>>> * Use Cypher query when finder method does not have a lucene
>>>> index,
>>>> >>> >>>> #210
>>>> >>> >>>> Changelog for neo4j-core:
>>>> >>> >>>> == 2.2.0 / 2012-10-02
>>>> >>> >>>> * Use 1.0.0 of neo4j-cypher
>>>> >>> >>>> * Fix of Neo4j::Config issue using boolean values,
>>>> >>> >>>> andreasronge/neo4j#218
>>>> >>> >>>> * The []= operator checks that the value is a valid Neo4j
>>>> value #16
I've been trying your updated gem, it works in general, but getting an error for omniauth. User is omniauthable, routes are ok, and, qhen I hit this url for twitter authentication, it throws the error below
> Most of the tests pass, mostly minor problems. You can see them updates in > the test/overrides folder. There is a strange issue with one of the devise > tests that is checking password confirmation validation, but I cannot > replicate it (that is, password confirmation works fine for me in the app > and in console). > I'll try and look into this ... eventually.
> you can try it out yourself: > gem install rails > rails new myapp -m http://andreasronge.github.com/neo4j/rails.rb -O > cd myapp > add to your Gem File : > gem 'devise-neo4j', :git => 'git://github.com/cfitz/devise-neo4j.git', > :branch => 'devise2' > bundle > rails generate devise:install --orm=neo4j > bundle exec rails g neo4j:devise User > add devise_for :users to config/routes.rb (not sure why generator is not > adding this...) > rails s > go to http://localhost:3000/users/sign_up, sign up, then go to > http://localhost:3000/users/ . Try and edit your password with a bad > confirmation....everything works as I'd expected it to.
> Otherwise, let me know what you think or if anyone sees any suggestions > for improvement... b,chris.
> On Mon, Nov 5, 2012 at 2:53 PM, arikan <ari...@gmail.com <javascript:>>wrote:
>> Thanks a lot Chris, Andreas,
>> Now devise-neo4j works fine, after the Gemfile.lock update, both >> with Rails 3.1.7 and Rails 3.2.8, and neo4j 2.0.0 and neo4j 2.2.0.
>> Burak
>> On Monday, November 5, 2012 3:08:57 PM UTC+2, Chris F. wrote:
>>> Ah, yeah, that would make sense....I removed the .lock file from github. >>> Let me know if that fixes the issue.
>>> I am thinking I ought to update this so it works with the newer version >>> of devise and update the tests. I don't have time today, but I'll try to >>> squeeze it in tomorrow...
>>> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andrea...@gmail.com>wrote:
>>>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>>>> >> I have a folk of these at https://github.com/cfitz/**devise-neo4j<https://github.com/cfitz/devise-neo4j>that I am >>>> >> using which should work with both the new version of neo4jrb and >>>> devise >>>> >> 2.0.4. However, I haven't added any tests to the gem since I am >>>> testing >>>> >> this in the application....maybe in a couple of days I'll add the >>>> tests and >>>> >> put in a proper pull request....let me know if you have any >>>> questions...
>>>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com> >>>> >> wrote:
>>>> >>> Hi
>>>> >>> I think it should work on the old devise < version 2.0. >>>> >>> Btw, according to this
>>>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote: >>>> >>> > Guys,
>>>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't >>>> >>> > expect it >>>> >>> > to work after so many changes happened in Neo4j.
>>>> >>> > Regards, >>>> >>> > Antonio
>>>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 and >>>> >>> >> other >>>> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same >>>> NameError: >>>> >>> >> uninitialized constant Devise::Schema
>>>> >>> >>> On Thursday, October 4, 2012 11:57:28 AM UTC+3, ronge wrote:
>>>> >>> >>>> Hi
>>>> >>> >>>> I've released version 2.2.0 of neo4j-core, neo4j-wrapper and >>>> the >>>> >>> >>>> neo4j >>>> >>> >>>> Ruby gems. >>>> >>> >>>> This release contains a new gem, the neo4j-cypher gem which >>>> also can >>>> >>> >>>> be used from the neography and none JRuby platforms. >>>> >>> >>>> I've also released the jars for the new Neo4j 1.8 >>>> (neo4j-community, >>>> >>> >>>> neo4j-advanced and neo4j-enterprise).
Looks like Omniauth is trying to add to the logger, but cannot...by default
it's STDOUT.. In your config/initializers/devise.rb (outside of
the Devise.setup block), try adding :
OmniAuth.config.logger = Rails.logger
On Thu, Nov 15, 2012 at 11:59 AM, arikan <ari...@gmail.com> wrote:
> Hi Chris,
> I've been trying your updated gem, it works in general, but getting an
> error for omniauth. User is omniauthable, routes are ok, and, qhen I hit
> this url for twitter authentication, it throws the error below
>> Most of the tests pass, mostly minor problems. You can see them updates
>> in the test/overrides folder. There is a strange issue with one of the
>> devise tests that is checking password confirmation validation, but I
>> cannot replicate it (that is, password confirmation works fine for me in
>> the app and in console).
>> I'll try and look into this ... eventually.
>> Otherwise, let me know what you think or if anyone sees any suggestions
>> for improvement... b,chris.
>> On Mon, Nov 5, 2012 at 2:53 PM, arikan <ari...@gmail.com> wrote:
>>> Thanks a lot Chris, Andreas,
>>> Now devise-neo4j works fine, after the Gemfile.lock update, both
>>> with Rails 3.1.7 and Rails 3.2.8, and neo4j 2.0.0 and neo4j 2.2.0.
>>> Burak
>>> On Monday, November 5, 2012 3:08:57 PM UTC+2, Chris F. wrote:
>>>> Ah, yeah, that would make sense....I removed the .lock file from
>>>> github. Let me know if that fixes the issue.
>>>> I am thinking I ought to update this so it works with the newer version
>>>> of devise and update the tests. I don't have time today, but I'll try to
>>>> squeeze it in tomorrow...
>>>> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andrea...@gmail.com>wrote:
>>>>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>>>>> >> I have a folk of these at https://github.com/cfitz/**devis**e-neo4j<https://github.com/cfitz/devise-neo4j>that I am
>>>>> >> using which should work with both the new version of neo4jrb and
>>>>> devise
>>>>> >> 2.0.4. However, I haven't added any tests to the gem since I am
>>>>> testing
>>>>> >> this in the application....maybe in a couple of days I'll add the
>>>>> tests and
>>>>> >> put in a proper pull request....let me know if you have any
>>>>> questions...
>>>>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge <andrea...@gmail.com
>>>>> >> wrote:
>>>>> >>> Hi
>>>>> >>> I think it should work on the old devise < version 2.0.
>>>>> >>> Btw, according to this
>>>>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote:
>>>>> >>> > Guys,
>>>>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so don't
>>>>> >>> > expect it
>>>>> >>> > to work after so many changes happened in Neo4j.
>>>>> >>> > Regards,
>>>>> >>> > Antonio
>>>>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>>>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0
>>>>> and
>>>>> >>> >> other
>>>>> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same
>>>>> NameError:
>>>>> >>> >> uninitialized constant Devise::Schema
On Thursday, November 15, 2012 1:19:36 PM UTC+2, Chris F. wrote:
> Hey Burak,
> Looks like Omniauth is trying to add to the logger, but cannot...by > default it's STDOUT.. In your config/initializers/devise.rb (outside of > the Devise.setup block), try adding : > OmniAuth.config.logger = Rails.logger
> Does that fix it?
> On Thu, Nov 15, 2012 at 11:59 AM, arikan <ari...@gmail.com <javascript:>>wrote:
>> Hi Chris,
>> I've been trying your updated gem, it works in general, but getting an >> error for omniauth. User is omniauthable, routes are ok, and, qhen I hit >> this url for twitter authentication, it throws the error below
>>> Most of the tests pass, mostly minor problems. You can see them updates >>> in the test/overrides folder. There is a strange issue with one of the >>> devise tests that is checking password confirmation validation, but I >>> cannot replicate it (that is, password confirmation works fine for me in >>> the app and in console). >>> I'll try and look into this ... eventually.
>>> Otherwise, let me know what you think or if anyone sees any suggestions >>> for improvement... b,chris.
>>> On Mon, Nov 5, 2012 at 2:53 PM, arikan <ari...@gmail.com> wrote:
>>>> Thanks a lot Chris, Andreas,
>>>> Now devise-neo4j works fine, after the Gemfile.lock update, both >>>> with Rails 3.1.7 and Rails 3.2.8, and neo4j 2.0.0 and neo4j 2.2.0.
>>>> Burak
>>>> On Monday, November 5, 2012 3:08:57 PM UTC+2, Chris F. wrote:
>>>>> Ah, yeah, that would make sense....I removed the .lock file from >>>>> github. Let me know if that fixes the issue.
>>>>> I am thinking I ought to update this so it works with the newer >>>>> version of devise and update the tests. I don't have time today, but I'll >>>>> try to squeeze it in tomorrow...
>>>>> On Mon, Nov 5, 2012 at 1:56 PM, Andreas Ronge <andrea...@gmail.com>wrote:
>>>>>> Only the gemspec file should give the ranges of version allowed for >>>>>> the devise-neo4j gem. >>>>>> Try remove the Gemfile.lock from the repo.
>>>>>> Cheers
>>>>>> On Mon, Nov 5, 2012 at 1:37 PM, arikan <ari...@gmail.com> wrote: >>>>>> > Hi Chris,
>>>>>> > I tried your devise-neo4j, it has the following dependency mismatch >>>>>> with >>>>>> > neo4j 2.0, is it a quick fix?
>>>>>> > On Monday, November 5, 2012 1:51:50 PM UTC+2, Chris F. wrote:
>>>>>> >> I have a folk of these at https://github.com/cfitz/**devis** >>>>>> e-neo4j <https://github.com/cfitz/devise-neo4j> that I am >>>>>> >> using which should work with both the new version of neo4jrb and >>>>>> devise >>>>>> >> 2.0.4. However, I haven't added any tests to the gem since I am >>>>>> testing >>>>>> >> this in the application....maybe in a couple of days I'll add the >>>>>> tests and >>>>>> >> put in a proper pull request....let me know if you have any >>>>>> questions...
>>>>>> >> On Mon, Nov 5, 2012 at 11:56 AM, Andreas Ronge < >>>>>> andrea...@gmail.com> >>>>>> >> wrote:
>>>>>> >>> Hi
>>>>>> >>> I think it should work on the old devise < version 2.0. >>>>>> >>> Btw, according to this
>>>>>> >>> On Mon, Nov 5, 2012 at 11:18 AM, Toni <nio...@gmail.com> wrote: >>>>>> >>> > Guys,
>>>>>> >>> > the devise-neo4j code was last modified on Sep 25, 2011, so >>>>>> don't >>>>>> >>> > expect it >>>>>> >>> > to work after so many changes happened in Neo4j.
>>>>>> >>> > Regards, >>>>>> >>> > Antonio
>>>>>> >>> > On Monday, November 5, 2012 3:46:56 PM UTC+8, arikan wrote:
>>>>>> >>> >> I am on jruby 1.7.0, also tried devise-neo4j with neo4j 2.0.0 >>>>>> and >>>>>> >>> >> other >>>>>> >>> >> versions of Rails (3.2.8, 3.2.7, 3.1.7) getting the same >>>>>> NameError: >>>>>> >>> >> uninitialized constant Devise::Schema