diff options
-rw-r--r-- | LICENSE | 16 | ||||
-rwxr-xr-x | README.md | 4 | ||||
-rw-r--r-- | activator.properties | 4 | ||||
-rw-r--r-- | tutorial/index.html | 19 |
4 files changed, 41 insertions, 2 deletions
@@ -0,0 +1,16 @@ +Included SQL code is taken from the Java SE tutorial and licensed under +http://www.oracle.com/technetwork/licenses/bsd-license-1835287.html . + +The rest of the project is + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + +http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. @@ -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. diff --git a/activator.properties b/activator.properties new file mode 100644 index 0000000..9121bd1 --- /dev/null +++ b/activator.properties @@ -0,0 +1,4 @@ +name=slick-codegen-example +title=Using Slicks default code generator +description= +tags=scala,slick,database,relational diff --git a/tutorial/index.html b/tutorial/index.html new file mode 100644 index 0000000..a77b4dc --- /dev/null +++ b/tutorial/index.html @@ -0,0 +1,19 @@ +<html> +<head> + <title>Using Slicks default code generator</title> +</head> +<body> + +<div> + <h2>Using Slicks default code generator</h2> + <pre> +This code example shows how to setup sbt to use Slick's preconfigued code-generator for working with an existing database schema. <code>project/Build.scala</code> enables automatically as well as manually triggered code-generation. <code>src/main/scala/Example.scala</code> uses the generated code. The code is generated into file <code>target/scala-2.10/src_managed/slick/demo/Tables.scala</code>, which can be changed in the sbt script. It is usally wise to keep the generated Slick code under version control. + +Use <code>sbt run</code> to run the demo. + +More info about Slick on <a href="http://slick.typesafe.com/docs/">http://slick.typesafe.com/docs/</a> + </pre> +</div> + +</body> +</html> |