io.getquill.codegen.model.PackagingStrategy
ByPackageHeader
Related Doc:
package PackagingStrategy
Use this strategy when you want a separate source code file (or string) for every single table.
Use this strategy when you want a separate source code file (or string) for every single table. Typically you'll want to use this when table schemas are very large and you want to minimize the footprint of your imports (i.e. since each file is a seperate table you can be sure to just imports the exact tables needed for every source file).
When you want each file (or string) to contain an entire schema, use this strategy.
When you want each file (or string) to contain an entire schema, use this strategy. This is useful for code-generators that have common code per-schema for example the ComposeableTraitsGen that creates Traits representing database schemas that can be composed with Contexts.