What do Java game developers use for Database persistence?

[Roquen]

I thought that it has a persistent data-store, but it's highly likely I'm mistaken.

[sproingie]

Akka has support for libraries like mongodb and redis, but only to use them as a durable backing for actor mailboxes, for when you need pending messages to survive restarts of the entire program.   Other than that, it's not concerned with storage at all.

[sproket]

That's pretty cool.  Similar to my design except I don't need POJOs to inherit anything special.   Well I spent a bit of time on this and posted it up on sourceforge.  I'll post something in the Share Code section.

Games published by our own members! Check 'em out!

[Nate]

I'm late to this party, but a friend of mine is working on a neat project:
https://code.google.com/p/fado/
I takes SQL you hand write and it generates Java classes. You then use the Java classes in your code, so you have a nice, type safe API for your queries. It parses the SQL and knows about the database schema, so it can be smart. I haven't seen this approach done before. Here's a little example:
https://code.google.com/p/fado/source/browse/trunk/source/play/PlayAllergies2.java
I've prodded him to put some examples on the front page.

Going the other way, trying to emit SQL with a Java API, doesn't seem to work too well. Hiding the SQL entirely is fine for simple cases but eventually you tend to need to go under the hood, and thar be dragons. Simple cases are easy to write the SQL for, and you write the best SQL for complex cases anyway. So write your SQL and use Fado to keep your Java source from getting nasty. That is the idea, I believe.

[ChristerSwahn]

I think you're right in that the ORM impendance mismatch is probably better bridged by generating classes from relations than the other way around. It's a cool concept your friend is pursuing! But it also hinges on the tools available within the language, making queries and such easier. And the two-step cross-language compilation process is always going to feel like a hurdle.

[Nate]

Aye, he says he has half an Eclipse plugin built.

[gimbal]

I've used Hibernate+JPA in the past but I find JPA based ORM a bit too clunky for "simple" client app usage, plus you always need half a dozen libraries of varying sizes just to be able to do basic persistence stuff. Since Play 2 started to default to EBean in stead of Hibernate I investigated it and found it a surprisingly neat and concise API that is for a change decently documented, updated quite regularly and to put icing on the cake is available through a maven repository; I'll certainly consider it for a future project.