Articles in the Databases Category
Is not a bug, but a pretty annoying configuration thing which appear when you try to configure Enhanced Broker Cluster in Glassfish. I configured my persistent store, for Enhanced Broker Cluster, as jdbc / MySQL:
Share this post
I searched over internet, on several tens of posts, to find how to delete a crashed Innodb table. Short story: I tried to import a big table but it crashed in the middle of the process (power failure). The table was not very important so I didn’t care about the table, I just want to delete it and start from the scratch, but surprise! The table cannot be deleted! I use the latest MySQL Innodb plugin from Debian backports repository (is coming with Debian 5.1.xx) with file per table …
Initially, DBAppender for Log4j was introduced in version 1.3 of Log4j, but this version was ABANDONED by Apache team. DBAppender is very useful when we want to send our log on a JNDI resource and not on standard JDBC or file. If you need just logging in a database for your application, then you should use JDBCAppender. If you want to log on a JNDI or Database Connection Pool the DBAppender is for you. In this post I will show you how to get, compile and quick test the DBAppender.
In my experiments with databases I was constrained to tune the system together with the databases. A system what will run a database is quite different from any other server system, because databases put a lot of stress on the IO and especially on the disks (probably the file servers too). Hardware is not all you should tune your system as much as possible. In this post I will talk about Linux with Ext3 (is what I have right now), but on future I will test OpenSolaris with ZFS.
We are living interesting times … MySQL was first purchased by SUN and now SUN was purchased by ORACLE. I don’t know what future will reserve for MySQL, but in this moment it seems MySQL is coming very very close to PostgreSQL. We are NOT talking about MySQL with MyISAM, we are talking about MySQL with InnoDB, because I’m directly interested in a set of properties what PostgreSQL already have them built-in and MySQL achieve them through InnoDB (and the new Maria Data plugin). This properties are Atomicity, Consistency, Isolation, Durability = ACID, in other words, very stable, good integrity and crash proof database. Why an ACID database? Sometimes we are more interested in ACID for our data than raw speed. For example do you keep your savings to a bank who is running a NON ACID database? I think you understand my concern.