[jdev] ejabberd vs. Wildfire

[Daniel Henninger]

>> First the environment. We're a small webhosting company that is  
>> actually
>> managed by my dad and me only, where I do the tech stuff. I'm running
>> that Jabber server to the public and primarily set it up for my  
>> personal
>> use. I don't expect more than a handful of users to show up there  
>> in the
>> near future (currently there's two users). So performance/scalability
>> isn't an important thing to me. I could even say I don't need a data
>> import facility right now, but that shouldn't be too often in the
>> future... In any case I'm going to use an open database (MySQL  
>> would be
>> good). I never managed to export that Erlang database thing  
>> (forgot its
>> name) and I somewhat dislike closed data storage systems.
>
> There is a migration tool in recent ejabberd versions.
> Native PostgreSQL support emerged in 1.0.0.
> Native MySQL support is in Subversion (and will be in 1.0.1 I guess).
> Documentation for SQL databases is in progress AFAIR.

Also, regarding Mnesia (the erlang database you are referring to), I  
just wanted to chime in real quick that you can get direct access to  
it.  I will never ever remember the commands to do so, but there's  
something you can do that brings up the entire database in what looks  
like a spreadsheet application, and you can edit/look at things  
directly.  =)  I really don't know where that's documented, and I  
still prefer a MySQL backend, but I did want you to know that you can  
get to the Mnesia database should you wish to.

Daniel