diff options
| author | Christopher Vogt <christopher.vogt@epfl.ch> | 2014-01-30 16:49:57 +0100 |
|---|---|---|
| committer | Christopher Vogt <christopher.vogt@epfl.ch> | 2014-01-30 16:49:57 +0100 |
| commit | 70d165e918037d7d68a90fa1accc63a9ee5bd7e9 (patch) | |
| tree | e9a4f731e1ed25f65a92996ce74f70d42619cd62 /README.md | |
| parent | 6daeac59e8db26c603976be4f2bdae00173baa3a (diff) | |
| download | slick-codegen-example-70d165e918037d7d68a90fa1accc63a9ee5bd7e9.tar.gz slick-codegen-example-70d165e918037d7d68a90fa1accc63a9ee5bd7e9.tar.bz2 slick-codegen-example-70d165e918037d7d68a90fa1accc63a9ee5bd7e9.zip | |
Turn into activator project
Diffstat (limited to 'README.md')
| -rwxr-xr-x | README.md | 4 |
1 files changed, 2 insertions, 2 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`. The location 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.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. -Use `sbt run` to run the demo.
\ No newline at end of file +Use `sbt run` to run the demo. |