When the Jdbc Typer sees a NUMERIC
jdbc column, should it use int/long
instead of BigInteger
if the scale allows?
When the Jdbc Typer sees a NUMERIC
jdbc column, should it use int/long
instead of BigInteger
if the scale allows?
When the Jdbc Typer tries to figure out which Scala/Java objects to use for which JDBC type (e.g.
When the Jdbc Typer tries to figure out which Scala/Java objects to use for which JDBC type (e.g. use String for Varchar(...), Long for bigint etc...), what do we do when we discover a JDBC type which we cannot translate (e.g. blob which is currently not supported by quill). The simplest thing to do is to skip the column.
The purpose of the simple code generator is to generate simple case classes representing tables in a database. Create one or multiple
CodeGeneratorConfig
objects and call the.writeFiles
or.writeStrings
methods on the code generator and the reset happens automatically.