André Rouél arouel

Free O'Reilly books and convenient script to just download them.

Thanks /u/FallenAege/ and /u/ShPavel/ from this Reddit post

How to use:

Take the download.sh file and put it into a directory where you want the files to be saved.
cd into the directory and make sure that it has executable permissions (chmod +x download.sh should do it)
Run ./download.sh and wee there it goes. Also if you do not want all the files, just simply comment the ones you do not want.

I am learning slick. A bit of tough road initially. The blogs and other posts out there really help. This tutorial was especially helpful.

My domain was storing note objects in database and tracking revisions. Here's the table structure:

 class Notes(tag: Tag) extends Table[(Int, Int, java.sql.Timestamp, Boolean, Option[String])](tag, "Notes") {
    // some dbs cannot return compound primary key, so use a standard int
    def id = column[Int]("id", O.AutoInc, O.PrimaryKey)
    def docId = column[Int]("docId")
    def createdOn = column[java.sql.Timestamp]("createdOn")
    def content = column[Option[String]]("content")

#The Problem We just described standard design issues you have when you start creating layers of services, DAOs and other components to implement an application. That blog/gist is here.

The goal is to think through some designs in order to develop something useful for an application.

#Working through Layers If you compose services and DAOs the normal way, you typically get imperative style objects. For example, imagine the following:

  object DomainObjects {

When you do your first Sonar run on your project, you get a lot of new quality numbers to play with, but no trends. You only have one data set for comparison, the now picture.

Wouldn't it be nice if you could see the current trend of the project without waiting a couple of month for the 'daily/weekly' Sonar runs to fill up the data? Well, you're in luck! And if you're using git as a version system as well, this is your day. :)

In the Sonar Advanced Parameter documentation you will find a System Property called sonar.projectDate. The property let you tell Sonar when in time the running analysis was ran.

By combining this property and what your version system does best, track changes to source, we can now play back the history of the project as far as Sonar is concerned.

This little Bash script illustrates the concept. To spell out what it does in human readable form:

	import java.util.function.Function;
	import java.util.Arrays;
	import java.util.List;
	import java.util.Optional;
	import java.util.stream.Collectors;

	public class Demo {

	/**
	* An IO operation that results in a value of type T.

	import java.sql.DriverManager
	import scalaz.concurrent.Task
	import scalaz.stream.io
	import scalaz.stream.Process.End

	class Query(query: String, chunkSize: Int) {
	Class forName "org.postgresql.Driver"
	val connection = DriverManager.getConnection(url, "username", "password")
	val statement = connection.createStatement
	// This will cause the postgres driver to create a cursor and give ResultSets of that size

	git fetch --all
	git reset --hard origin/master
	git pull origin master