florinpatrascu/closure_table

Closure Table for Elixir - a simple solution for storing and manipulating complex hierarchies.

closure_table's Issues

Version 1.0.11 is not available on hex.pm

Please publish the latest version on hex.pm for an easier dev experience.

use `distance` instead of `depth`

distance is more make sense; that's meaning the distance between two nodes.

depth also means the tree depth.

Ecto adapter fails to accept anything other than integers for IDs

Was attempting to use this in a database that uses :binary_id as the primary ID type on all tables, but it immediately failed.

Mainly due to this line: https://github.com/florinpatrascu/closure_table/blob/main/lib/cte/adapter/ecto.ex#L309

This is the error thrown:

** (Ecto.Query.CastError) deps/closure_table/lib/cte/adapter/ecto.ex:307: value `"f74992a5-2ec4-438c-bfc4-97a31c925d0f"` in `select` cannot be cast to type :integer in query:

Immediate parent or child query

To be able to query immediate parent or child, the simplest way is to add depth (or level or what is your preference) column to tree_paths table

descendants/2 and ancestors/2 will accept a new option called depth (or whatever that matches the new column).

Thanks for making this package, I am evaluating and would love to contribute, but it would be great to hear from author before introducing public data structure breaking change (e.g. change paths to list of map instead.)