Looks good.

I know that issues where the schema is different are always going to be a problem (nothing can save you there unless you want auto generated entities every time) but I can live with that.

How are you dealing with issues like the one I found the other day.

A view was created in MySQL which selected from a table with a column compressed with the compress function and was uncompressed in the view.

IE

select id,uncompress(content) as content from stuff;

The above looks fine, but unless you cast the content to a char most ORM's have issues working out what it is, yet it looks fine in your standard mysql command line query. It's an unusual case, but I would like to see the autogenerated code produce a binary cast so I can explicitly see the error when I generate rather then at runtime.

That, unforunately, I can't help with. Like any SQL DSL I've worked with, there's a few features that still aren't fleshed out... yet. I have complete faith they will flesh them out if prompted by the community. After that, you'll have to use pure SQL and cross your fingers.

Oh well. If its decent enough I can live with this single issue as I catch it pretty easily though integration tests.