aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorChristopher Vogt <christopher.vogt@epfl.ch>2013-12-23 08:11:12 +0100
committerChristopher Vogt <christopher.vogt@epfl.ch>2013-12-24 18:22:21 +0100
commitc952071e9beb0124360b65b127ab571dd8d9f970 (patch)
tree48ce3b33000c57649f9a5189964e5ddbe9ccaf48 /README.md
downloadslick-codegen-example-647b0fb8d7aeb5f9c059c4584ad5065322c3759f.tar.gz
slick-codegen-example-647b0fb8d7aeb5f9c059c4584ad5065322c3759f.tar.bz2
slick-codegen-example-647b0fb8d7aeb5f9c059c4584ad5065322c3759f.zip
Initial code example2.0.0-RC1
Diffstat (limited to 'README.md')
-rwxr-xr-xREADME.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/README.md b/README.md
new file mode 100755
index 0000000..1e542c2
--- /dev/null
+++ b/README.md
@@ -0,0 +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.
+
+Use `sbt run` to run the demo. \ No newline at end of file