Database connection pool example with c3p0

[fernandezpablo85]

No description provided.

[fernandezpablo85]

don't you guys want this? /cc @szeiger

[szeiger]

Sorry, I must have missed this. Yes, we should use this (in fact, I'd like to add better support for connection pooling to the core, but an example would be a good starting point).

[fernandezpablo85]

Feel free to pull it in then. I also wrote about slick connection pooling here:

http://fernandezpablo85.github.io/2013/04/07/slick_connection_pooling.html

[fernandezpablo85]

Is this going in?

[szeiger]

It would be great if you could publish this example as an Activator (http://typesafe.com/activator) template instead. We're trying to get rid of slick-examples for 2.1 and replace it by individual Activator templates (slick/slick#603). So far we have only created the The "Hello Slick" template which is is an updated version of "FirstExample" from slick-examples. A template is basically a standalone sbt project with a documentation file that is displayed in Activator's sidebar. You can publish a template on your own and keep to your own schedule for updating it. If you tag it with "slick", users can find it easily in the Activator UI.

[fernandezpablo85]

Ok, I know nothing about the activator templates but it's a good excuse to
get used to them.

On Mon, Jan 27, 2014 at 12:10 PM, Stefan Zeiger [email protected]:

It would be great if you could publish this example as an Activator (
http://typesafe.com/activator) template instead. We're trying to get rid
of slick-examples for 2.1 and replace it by individual Activator templates (
slick/slick#603 slick/slick#603). So far we
have only created the The "Hello Slick" template which is is an updated
version of "FirstExample" from slick-examples. A template is basically a
standalone sbt project with a documentation file that is displayed in
Activator's sidebar. You can publish a template on your own and keep to
your own schedule for updating it. If you tag it with "slick", users can
find it easily in the Activator UI.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/19#issuecomment-33374996
.