Ari Pollak wrote:
In any case, I don't think it wise to add/remove databases on
installation/removal, that should probably be left up to the user to do
- I don't think any package, including TWIG, which needs MySQL to run,
installs a database automatically.
I believe that IMP does some questi
On Sun, Jun 16, 2002 at 01:25:22PM -0400, Ari Pollak wrote:
> The standard way of storing the root password for MySQL is in
> ~root/.my.cnf.. It should look something like this:
> [mysqladmin]
> user= username
> password= password
> In any case, I don't think it wise to add/r
The standard way of storing the root password for MySQL is in
~root/.my.cnf.. It should look something like this:
[mysqladmin]
user= username
password= password
In any case, I don't think it wise to add/remove databases on
installation/removal, that should probably be left
Hi ya,
I am currently trying to package RefDB, a bibliography database
manager. RefDB uses MySQL, so one thing that the package has to
do is to create/delete MySQL databases and users. For that, the
scripts need the admin password for the MySQL database server.
What is the best way to handle t
The standard way of storing the root password for MySQL is in
~root/.my.cnf.. It should look something like this:
[mysqladmin]
user= username
password= password
In any case, I don't think it wise to add/remove databases on
installation/removal, that should probably be left
Hi ya,
I am currently trying to package RefDB, a bibliography database
manager. RefDB uses MySQL, so one thing that the package has to
do is to create/delete MySQL databases and users. For that, the
scripts need the admin password for the MySQL database server.
What is the best way to handle
6 matches
Mail list logo
