Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add an option database_type #374

Closed
wants to merge 1 commit into from
Closed

Add an option database_type #374

wants to merge 1 commit into from

Commits on Jan 17, 2021

  1. Add an option database_type 

    Problem: When using `numeric_ordering: true`, closure_tree tries to find out the type of database during the initialization process. This can be problematic, for example when doing `rails db:create`, in which case there is no database, yet. Another scenario is `rails asssets:prcompile` in a Docker container that is being made for production, but it doesn't have access to the production database yet, because it isn't rolled out, yet.

Solution: I have added an option to specify the database_type manually. This option is *only* used then numeric_ordering is set to `true`
    @markusherzog @n-rodriguez
    markusherzog authored and n-rodriguez committed Jan 17, 2021
    Configuration menu
    Copy the full SHA
    460a340 View commit details
    Browse the repository at this point in the history