By woodjr on May 24, 2007
The first question my boss asked after I got the Slynkr code released as a java.net project: where can I file an RFE for it to install with one click using a JavaDB back-end? Then, as if on cue, the first outside message on the project's dev aliases followed suit: "What are your thoughts about other support for other databases (ie, MySQL and/or Postgres)?"
I may be slow, but I think I see the message. People might just want to use a database other than Oracle (which is what we used for our initial development of Slynkr). Well, guess what? You can do it.
It's not yet a one-click install process (sorry, Eduardo). And I personally haven't yet tried things out with MySQL or PostgreSQL (sorry, Nick). But I do now have instructions for running Slynkr using a JavaDB back-end (aka Apache Derby). If you're wanting to get your own instance of Slynkr up and running, this is currently your best bet. After all, Oracle is a nice database but it's a lot of overhead for just trying something out.
So please, give it a shot. If you run into problems, let me know. Or if you see ways to make things better, update the instructions (that's why they're on a Wiki, after all).
Oh, and by the way... I think that at least MySQL support should be pretty easy also. Here at Sun, we actually have an internal Slynkr instance which is using MySQL. I just don't have instructions for it (yet).