Great blog by Chet Haase on the new Consumer JRE.
A common question we get on the derby-user list is how to talk to a Derby database running in embedded mode from a separate client, such as a report tool or visual query tool.
You can do this by
starting a network server in the same VM as the embedded database.
I know I mentioned this in my
overview of the JavaOne keynote, but if you blinked your eyes, you may have missed it.
My little sister, Elizabeth Van Couvering, is in the graduate program at the London School of Economics (lucky cad, she was born in England and has dual citizenship).
I think there is a lot more to choosing a database than performance. Yes, performance is important, and all other things being equal, it's a very good way to help you choose a database vendor.
What's problematic is that published performance numbers can often be misleading.
Most databases provide a command-line tool to run SQL that you've put in a file.
I just learned the term "schwag" at this JavaOne. I am so behind the times. I don't even know if I'm spelling it right.
You may have
read my blog about my concerns around technology. At the same time, I also believe that if you are conscious and committed and vigilant about how you use it, technology can be a huge enabler for helping make a difference in people's lives.
The first year we had a booth for Apache Derby/Java DB at JavaOne, it was kind of sad. Nobody had heard of us, or even understood what we were about. We spent most of our time chatting amongst ourselves and with other Sun employees.
The second year was a little busier, but mostly it was "so, what is Java DB anyway?"
This year couldn't be more different.
I went to the Linda Lemichiel's session on what they're
planning JPA 2.0. I thought I'd summarize what I heard.
Note - at the end of the blog I provide an email address
you can use to provide feedback for what you want to see in JPA.
This is really important.