MySQL Question

[Brian Densmore]

You could always use Postgres. It's faster (mostly), more SQL compliant,
includes record level locking and is ACID compliant (Atomicity
Consistency Isolation Durability). True MySQL will have all this
functionality in version 4.1, and the alpha version 4.0 has some of
this, it's just not there yet.

> -----Original Message-----
> From: Don Erickson [mailto:derick at shark.zeni.net]
> Sent: Wednesday, February 13, 2002 5:26 PM
> To: kclug at kclug.org
> Subject: Re: MySQL Question
> 
> 
> In article <MBBBJKFLMPDAKFLJOPIKMECJCJAA.s.dimbert at FHMR.com> 
> you write:
> >
> >The install instructions tell me to run:
> >
> >bach> /path/to/perl make_databse.pl -install
> >
> >...but, when I do, I'm told my username/password is wrong. 
> I've tried both
> >my master username and "undef", as instructed by the install guide.
> 
> If you've defined a password for root (as you should have) 
> then you need
> to supply a root password to either create the database as 
> root, or create
> a user and give it the needed permissions to create a database.
> 
> It may be that your perl script doesn't supply a password, and so it
> fails.  The standard way to create database would be something like:
> 
> # mysqladmin -u root -p<password> create databasename
> 
> Without the -p flay and an argument with no space between, then no
> password is supplied.  You might check and see what the perl script is
> trying to do.
> 
> 
> -- 
> Regards,
> 
> -Don
> 
> 
> majordomo at kclug.org
>