diff options
| author | Jan Christopher Vogt <oss.nsp@cvogt.org> | 2017-03-07 06:13:50 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-07 06:13:50 -0500 |
| commit | 5386ee4deae0cbd3e5f825cc724b7a7b5f95589b (patch) | |
| tree | 817e615e187f2a54aa76cd6281a97e9ee8d60b47 | |
| parent | 5938b1a51e7ad157f6d2018886c5b5d1d51481a3 (diff) | |
| download | slick-codegen-example-5386ee4deae0cbd3e5f825cc724b7a7b5f95589b.tar.gz slick-codegen-example-5386ee4deae0cbd3e5f825cc724b7a7b5f95589b.tar.bz2 slick-codegen-example-5386ee4deae0cbd3e5f825cc724b7a7b5f95589b.zip | |
| -rwxr-xr-x | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1,3 +1,3 @@ -This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. `project/Build.scala` enables automatically as well as manually triggered code-generation. `src/main/scala/Example.scala` uses the generated code. The code is generated into file `target/scala-2.11/src_managed/slick/demo/Tables.scala`, which can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control. +This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. `build.sbt` enables automatically as well as manually triggered code-generation. `src/main/scala/Example.scala` uses the generated code. The code is generated into file `target/scala-2.11/src_managed/slick/demo/Tables.scala`, which can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control. Use `sbt run` to run the demo. |