This seems to be the way things are with mysql nowdays.

Is it not time for the developers to take a serious look 
into culling all the outdated and multiple ways of 
accomplishing the same thing from mysql and the 
documentation?

All the excess documentation for different ways of 
accomplishing the same outcome makes the learning curve 
for mysql alot harder.

It doesn't make things any easier for people that want to 
take the MySQL certification exams either.

Why should we have to remember many different ways to 
accomplish the same thing, when one or two ways at the most 
would be quite sufficient?

For example, do we really need so many ways to start a 
server?

Do we really need different ways to add or drop indexes and 
modify tables?

With the newer versions of mysql (5.0.21+ or maybe version 
6.0.x), can we not dump the old syntax that is in mysql for 
backward compatibility reasons?

I would really like to see a slim and trim version of mysql,
the SQL commands, and the supporting cli programs, 
that is up to date and has a very fast learning curve.

Just my little gripe.

Kind Regards

Keith Roberts

In theory, theory and practice are the same;
in practice they are not.

On Sun, 11 Jun 2006, Gaspar Bakos wrote:

> To: mysqllist <mysql@lists.mysql.com>
> From: Gaspar Bakos <[EMAIL PROTECTED]>
> Subject: my-huge.cnf quite outdated
> 
> Hi,
> 
> Isn't the my-huge.cnf in the MySQL 5.0.22 distribution quite outdated?
> It says "for systems with 512Mb RAM or more". Nowdays this is pretty
> basic setup, and 'huge' is probably something in excess of 4Gb RAM.
> 
> I wonder if anyone has a recommendation for truly huge systems. For
> example a dual CPU AMD opteron system with 4Gb (or 8Gb) RAM that is
> fully devoted to serving the mysql daemon.
> 
> The config I have (see below) has been tuned to be optimal for creating
> indexes on a large (100Gb+) single database table. It works fine
> (although not satisfactory), but I worry that some parameters may have
> an optimal value or range, and it does not make sense to increase them
> like crazy.
> 
> Any opinions of the following : ?
> 
> [mysqld]
> key_buffer_size=1024M
> myisam_sort_buffer_size=256M
> sort_buffer_size=256M
> bulk_insert_buffer_size=64M
> join_buffer_size=64M
> max_connections=5
> read_buffer_size=8M
> read_rnd_buffer_size=8M
> net_buffer_length=1M
> max_allowed_packet=16M
> 
> # Cheers,
> # Gaspar
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
> 
> 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to