Note: if we had DRY working for blogs, then I could have just embedded the content from
my other blog and not have had to enter things in twice. Posting a link is not the same as having the content immediately available, which is why I decided to just copy the blog.
I know this isn't my main blog page any more (I'm hanging out at http://davidvancouvering.blogspot.com),
but I wanted to reach out to you all and get your input.
We are looking at what we want to do next with database toolin
I've decided to move my blog to a new location. You can now find me at http://davidvancouvering.blogspot.com.
Why am I making the move? Well, this was a hard decision.
Open source continues to amaze me. For so many years, I have worked on projects where customers would clamor for features, and we just didn't have enough time in the day or people to get them all built. We would say "yeah, that sounds cool" but with all the other things on our plate, when would we ever get to it?
Well, in open source, it's a whole different ball game.
Derby 10.3 beta
is available for testing. If you are using Derby/Java DB, you should try your local tests with this beta and make sure everything's working for you.
This page describes what's in this release.
I noticed today that I had 754 messages in my Spam folder in Gmail.
I decided to open the folder, and GMail had decided to place the following sponsored link at the top of the folder:
"Spam Vegetable Strudel - Bake 20 minutes or until golden, serve with soy sauce"
I just did a refresh, and now it says "Spam Imperial Tortilla Sandwiches - To serve, cut each roll in half"
I am a techie, and generally am not interested in the legal world. That changed a bit when I got into open source, where just to be able to contribute code you have to have some pretty solid understanding of open source licenses.
I wasn't sure what to think when I heard Sun's general counsel, Mike Dillon, had started a blog.
The default behavior of Java DB is that you have two level of access control: full access and read-only. Again, this is I believe due to the legacy of Cloudscape being originally an embedded-only database.
As I mentioned in my previous blog, Java DB's legacy is in the embedded world, where there is no such thing as sending the password over the wire.
But when you introduce the network client, this becomes an issue. And sending users and passwords in the clear is just not acceptable.
The original Cloudscape was built as an embedded-only database -- that is, it could only run inside the VM of another application. It did not have a client/server mode. That was added later.
In some areas, Java DB continues to carry have this embedded "legacy" with it. One particular area you should be aware of is authentication and authorization.