The title of this post may be a bit confusing--what does Neo4j have to do with Spray JSON? (I know that they both run on the JVM, don't try to be a smart ar*e.) Neo4j is a graph database and to make it useful for our systems, the vertices and edges can have properties. These properties can be Strings, numbers, Dates and such like. So, how are we going to squeeze rich structures in our objects into these (scalar) properties?
Just a short post before bed-time. I've added support for iteratees and composition for the different operations you may want to support. It is actually very useful. Let me demonstrate on a short example:
Welcome to another week in #Scala! It's been a busy week this week so there's loads to tell you about:
New Stuff
Typesafe released stbscalariform 0.2.0, a #sbt plugin for the scalariform source formatter.
If you are doing a lot of development with Scalaz, you're no doubt using the fancy function names, and special symbols like eta, lambda, alpha, and many others. To make your Scalaz typing easier, I have a keyboard layout maps the "fancy" letters to roman characters with the Option & Option + Shift modifiers. I've also added the long equals operator for the Scalad queries.
Welcome to another week in #Scala! Plenty to tell you about this week, and of course #devoxx has been taking place so check out parleys.com for all the presentations!
New Stuff
Scala+GWT, a project which aims to compile Scala code for the browser via the GWT toolchain, has reached milestone 3. This latest release adds support for Eclipse.
As part of the work on Scalad, I needed to be able to easily express queries that will be executed against the underlying data store. I did not want to use plain Strings, such as "((column = 'value') or (otherColumn > 5))". Having to construct strings like this one scream SQL injection!
I like the idea and syntax of ActiveRecord pattern; specifically, I like to be able to use the pattern obj.persist, obj.delete and so on, in Scala, a typesafe language. Before I continue, let me dismiss polluting the domain objects with the persistence-like mathods. That goes against all principles of layered programming.
I like Spring Framework's transactional support, especially the transactional aspects. The aspects, in combination with various implementations of the PlatformTransactionManagers and AspectJ's load-time weaving let me use declarative transaction management. So, in Spring, I can have
I've always loathed using <T> T requiredSingleResult(Collection<T> results), <T> T singleResult(Collection<T> results) and <T> T uniqueResult(Collection<T> results)to verify that some collection of objects contains a single result and to extract that single result. It's not that there's something inherently wrong with the DataAccessUtils metods, but the idiom of their usage is dreadful. It usually goes something like this:
I have been playing around with my ScalaData project. As I said on cakesolutions.org, we are working on a Scala project that aims to:
