I'm working on a java application which makes an extensive usage of hibernate's relation mapping system. The later offers several ways to define association mapping. We mostly use many-to-one relation declarations. The problem comes from the database. It's a pre-relational, pre-transactional, legacy database running on a prehistorical IBM zSeries host. The data on this database is very often dumb or corrupted. The lack of a proper referential integrity support and the foolish design make us end up quite often following non-existent relations.

Happily, hibernate provides a semantic which allow the application not to bother when a relation is missing, just as the legacy app does. This semantic is the not-found="ignore" parameter on the relation definition.

However, the usage of this semantic resumes to open very wide the doors to oblivion.

[Read More]

I'm looking for a new phone. The 3 models I found appealing are the ones mentioned in the title of this post. I'm posting here the criterions I ran through when looking at these phones and the reasons that make me choose one or the other.

[Read More]

Functional programming addicts,

I'm following an Haskell programming course. It was a short course, though we ran pretty much completely through the book "Programming in Haskell" by Graham Hutton. My personal view on this is that Haskell is a great language which offers a concision rarely reached by other languages, even other functional ones. The book sucks though. It's follows a way too much theoretical approach which makes it quite cumbersome and not interesting at all.

I've been told though that Hutton's book is the reference for Haskell programming. On my side I really found the various tutorials I could find online much more useful than the thorough lecture of this book I've been pretty much forced to follow.

Anyway, as usual I made a nifty summary on this book, so help yourself :

Haskell summary

The summary stands on three A4 pages and should serve as a reference for those who are initiated to Haskell programming and seek for a quick programming reference.

Happy reading, HTH

Guys,
I have written a quite amazing summary on the book "Introduction to the theory of computation" by Michael Sipser. It's definitely not a replacement for the book itself as it lacks the basic explanation required to understand the presented concepts. But if you have read this book and you're looking for a short summary standing on 7 A4 pages, there you have it.

The summary focuses on the most important concepts presented by the book and holds the mandatory illustrations going along the various concepts. Well there isn't much more to say about it, so if you have read that book, check out this summary. You should be pretty amazed to see that pretty much everything actually is in it ... in less than 7 pages.

It's worth to mention though that it's quite a big file (3.8 Mb).

Summary Theoretical Computer Science

Good reading, HTH

This is mostly a place for a few thoughts about technology, software engineering or generally computer sciences I want to share. There have been a lot of hot topics in my techno-life lately and I felt a blog is the right way to keep track of them. Yet that's far from being the only thing I will use this blog for, there are times when I just want to shout at something in a very public way or, you know, things that thrill me or piss me off or whatever. And I need a place to keep my resume or so.