Introspection fails: "This function must not be called on compound database names." (report 1301)

While introspecting with prisma2 (preview20). The error is pretty generic, I don’t know what part of the schema fails.

Schema parsing
thread 'main' panicked at 'This function must not be called on compound database names.', libs/datamodel/core/src/dml/traits.rs:14:13
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:77
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:61
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1028
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1412
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:65
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:50
   8: std::panicking::default_hook::{{closure}}

[tontonrally]

@janpio sorry mate, I had no time

In order to inform, I didn’t manage to get things working with the alpha branch, I tried a week ago. But, with the preview023, I manage to do the introspection without errors + generate the client and connect to the db. 👌

Thanks

[janpio]

Thank you very much for this bug report, I can reproduce the output you posted with the data included in the error report - so we can now look into this.

It’s the first time I see an error message like this, so I will ask my colleagues what is going on here.