The people who are using it to cause damages already know how this is done. The only dangerous part about something like this is that the public might be made aware of just how far from secure most financial transactions are.

There are lots of views on morality, but for me personally, I'd say yes, cheating is ALWAYS bad, because above all, it's dishonest. More than that though, you are cheating yourself, and your professed parter, and even your person on the side out of a chance at a real love relationship. If you have real and significant problems with your spouse, get those issues out in the air. If they can't be worked on between the two of you, get some counseling, or get some papers filed. It's really that simple. "Staying together for the kids" only teaches the children that abuse and unhappiness are okay as long as you can justify it to yourself. Besides, they learn almost everything about love relationships by watching their parents. If you don't love someone, but you're staying with them anyway, expect your kids will do the same until or unless they learn better. It's a complex problem to be sure, mainstream media has stressed the fairy tale courtship, where the magic of love is all about finding the right person. Unfortunately most people find out falling in love and living in love can be rather different. If you find the right person though, and you inspire each other to each be the right person for one another then you may wake up every day feeling like you are the luckiest person alive.

I fixed it for you. This is /. after all: The sooner MS can kill it self off, the better the entire planet will be.

I use MySQL and PostgreSQL every day and whenever I have a choice, and if it makes sense for the project, I reach for Postgres. MySQL may have better GUI tools and I'm sure that's important for some people, but PostgreSQL just works more like I want / need a database to work. For the kind of work I do (non trivial queries with a significant degree of write operations), it's as fast or faster than MySQL in any area that matters. If you don't see any perceived benefit to using a more robust, more compatible SQL implementation, then you probably aren't using a lot of what most RDBMS systems have to offer. And that's fine! There are plenty of places where people are using a database as a glorified storage box for object persistence where any fancy SQL stuff is almost a waste and that's a place where something like Drizzle makes a lot of sense.