Bruno Friedmann wrote:
> Hi dear Bacula'ers !
> 
> I've one customer where we will change the server hardware to a new one.
> ( changing also from 32bits to 64bits opensuse Linux )
> 
> We use now many projects with postgresql database, and mysql was just keep 
> for historical reason
> (bacula running with form the 1.3x version to the new 3.0.2)
> 
> Is it a good advice to change bacula from mysql to postgresql ?
> 
> I've check how the database is dumped ( It's pure mysql dump format but could 
> be manually changed )
> 
> I've planned to dump the mysql in a most portable way ( perharps csv ) and 
> reload data inside postgresql
> after a clean fresh create_database.
> 
> Is there any trouble with this path of doing things ?
> Did someone already do this manipulation ?
> 
> Thanks for all comments
> 

So a day later, digging into my idea it reveal some good and bad things.

Forget using csv, there's too much trouble with the NULL char. between the two 
db engines.

You have to forget also bunch bulk insert as postgresql and mysql are not the 
same table
(The fields are not in the same order !!! ) forcing full extended insert with 
adding each columns name.

Beside that, and some minor error on timestamp being invalid (out of range) for 
postgresql '0000-00-00 00:00:00' which I've
replaced by script to NULL I've successfully inserted the old mysql db to the 
postgresql engine.

Now I will try if bacula would recognize all of it's records.

More would be follow.

-- 

     Bruno Friedmann

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users