diff options
| author | krrrr38 <k.kaizu38@gmail.com> | 2015-08-09 21:42:53 +0900 |
|---|---|---|
| committer | krrrr38 <k.kaizu38@gmail.com> | 2015-08-09 22:33:15 +0900 |
| commit | 76ee13c8818bb386ba94a5c02037deb0ed7046c9 (patch) | |
| tree | 17e63ee59ff1f218e0692cd414a3d1b31a2930f1 /README.md | |
| parent | b40dfa417eaf77216ebe5df7d2a80dd6f521dd02 (diff) | |
| download | slick-codegen-example-76ee13c8818bb386ba94a5c02037deb0ed7046c9.tar.gz slick-codegen-example-76ee13c8818bb386ba94a5c02037deb0ed7046c9.tar.bz2 slick-codegen-example-76ee13c8818bb386ba94a5c02037deb0ed7046c9.zip | |
Update build for 3.0.1
Diffstat (limited to 'README.md')
| -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.10/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. `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. Use `sbt run` to run the demo. |