Hi John.
Thanks for your comment.
You are right. I als think that option
A is the best, but the problem, as you mentioned, it is only suitable for knowlegeable, that I might is not the general case. The "normal" end user only wants to use the software without knowing anything about data bases etc. I think the only suitable option is
C, taking into account that maybe is not the most efficient, in terms of memmory or disc consumptions.
And thanks for the comment about IO port. You are right. If we installl a separate paralell distribution, we should change the IO port defined by default.
Thanks again!!!!!!!!
2009/2/8 John R Pierce
<pierce@hogranch.com>Iñigo Barandiaran wrote:
Thank you all for your answers!.
This solve one of my problems :) THANKS!!!
John, thats a very good question. I've already thought about that, but I've no idea how to act yet. Becuase, as you said, if there is already a posgre Database server installed in the target system, and I dont know the password, what can i do? I can not delete the existing user account because I would be affecting other software. What about if I create another service user account, with a different name, such as MyPostgreUserAccount? That way I ensure that I'm creating/deleting the Postgre User of my application. What do you think?
perhaps a better option would be to notify the user that postgres was already installed on the system, and ask the user if
A) they want to use the existing postgres (which would have to be version 8.something you require naturally) and if so, what the postgres account password is so you can create your databases (note this isn't the service account password, this is the password of the postgres database superuser.
or,
B) if they don't want the current postgres, tell them they can uninstall it via add/remove and restart your installler
or,
C) said seperate parallel installation, with its own dir, port, and account.
obviously, option A) is only suitable for the knowlegeable user.