All Versions
192
Latest Version
Avg Release Cycle
58 days
Latest Release
910 days ago

Changelog History
Page 12

  • v6.1.0 Changes

    January 01, 2016

    🔄 Changed

    • When a model_class is specified on an association which is not an ActiveNode model, an error is raised
    • The model_class option on associations can no longer be a Class constant (should be a String, Symbol, nil, false, or an Array of Symbols/Strings)
    • The rel_class option on associations can no longer be a Class constant (should be a String, Symbol, or nil)
    • The from_class and to_class arguments can no longer be a Class constant (should be a String, Symbol, :any, or false)
    • ActiveNode and ActiveRel models can now be marshaled (thanks to jhoffner for the suggestion in #1093)

    🛠 Fixed

    • 👀 Inheritance of properties in ActiveRel is fixed (see #1080)

    ➕ Added

    • config/neo4j.yml now renders with an ERB step (thanks to mrstif via #1060)
    • #increment, #increment! and #concurrent_increment! methods added to instances of ActiveNode and ActiveRel (thanks to ProGM in #1074)

  • v6.0.9 Changes

    🛠 Fixed

    • Fix to find_in_batches (thanks to ProGM / see #1208)

  • v6.0.8 Changes

    🛠 Fixed

    • 🛠 Fixed issue where backticks weren't being added to where clauses for with_associations

  • v6.0.7 Changes

    August 03, 2016

    🛠 Fixed

    • Issue where creating relationships via has_one association created two relationships

  • v6.0.6 Changes

    🛠 Fixed

    • 🚅 Issue where inspect failed outside of Rails (Thanks to louspringer, #1111)

  • v6.0.5 Changes

    🛠 Fixed

    • 🛠 If a property and a scope have the same name, a "Stack level too deep" error occurs. Fixed by removing the instance method which scopes define. Could break something, but I very much doubt anybody is using this, and if they are it's likely a bug (#1088)

  • v6.0.4 Changes

    🛠 Fixed

    • When a model_class is specified on an association which is not an ActiveNode model, an error is raised

  • v6.0.3 Changes

    🛠 Fixed

    • Fixed issue where find_or_create was prioritizing property`s default value rather than what was being passed in (Thanks to brucek via #1071)

  • v6.0.2 Changes

    🛠 Fixed

    • 🛠 Fixed issue where association setting can't be set on initialize via #new (#1065)

  • v6.0.1 Changes

    🛠 Fixed

    • #with_associations should use multiple OPTIONAL MATCH clauses instead of one so that matches are independent (behavior changed in Neo4j 2.3.0) (forward ported from 5.2.15)