On Tue, 2009-05-19 at 15:02 +0530, Mrugesh Karnik wrote: > This is brain-dead! > > Best is to just ask the user to have a database with the appropriate access > details ready. > > As it is, for a desktop app, it doesn't make sense to tell user to go > configure a postgresql or even mysql database. Why not just use sqlite or > mysql embedded instead? > > Requirement of postgresql for a desktop app is just plain dumb, even for a > fan > such as myself. > > Suddenly, the mysql embedded move by amarok and akonadi devs makes sense > (if it didn't already). > > Mrugesh 1, We want a system that scails well and being deeply involved with both the databases (and db wars not intended ), postgresql is the right choice. Any ways we don't want to have 2 db back-ends for 2 different users. that is to say, postgresql gives us the features we need and mysql by all means doe not even come close to what we are getting from pg. 2, the user does not have to configure the database. That's is presisely the reason we are using the postgres user, yet what kenneth suggested is very much valid regarding the password and it has been on our mind and right now we are into deployment work where we actually did just that. 3, We are fast moving towards a web app for specially targetting the enterprise level deployment and the web admins or sys admins will be provided trainning for all that is needed.
happy hacking. Krishnakant. -- http://mm.glug-bom.org/mailman/listinfo/linuxers
