Provide model definition when using ref override

Hi,

This is a suggestion for the model definition provider.

Sometimes an override is used for ref in dbt projects and it would be really nice to have the model definition shortcut working in such cases.

Example override:

{% macro ref_no_db(model_name) %}
  {% do return(builtins.ref(model_name).include(database=false)) %}
{% endmacro %}

Suggested solution: override macro must start with “ref_” to simplify parsing.

[mdesmet]

If your overriden ref is not smart enough, then make it smarter: You can get the current scheme and current database and compare it towards the input, if it’s not the same you keep the database.

[rodik]

This is the override we ended up with:

{% macro ref(model_name) %}

  {% if config.get('materialized') == "view" %}
    {% do return(builtins.ref(model_name).include(database=false)) %}
  {% else %}
    {% do return(builtins.ref(model_name).include(database=true)) %}
  {% endif %}

{% endmacro %}

Views are really the only type of model where 2-part names are needed. Everything else defaults to original ref and 3-part names.