RE: MySQL 4.1.1 has been released

2003-12-05 Thread Boehn, Gunnar von
Hallo Lenz,


> From: Lenz Grimmer [mailto:[EMAIL PROTECTED]

> > Any chance to offer binaries for PowerPC Linux as well ? (Preferable
> > tgz)
> 
> Yes, we plan to offer Linux/PPC binaries in the near future - we're
> currently working on purchasing a system for that.

If you have some harddisk space left,
then you can install Linux on one of your MACs.


> I have not decided which Linux Distribution to use,
> though - maybe Yellowdog?

My recommendation would be, as always, Debian. :-)
But thats a metter of taste.

You can install nearly every distro on PPC.
Good examples are: YellowDog, Mandrake, Red Hat, Suse, Gentoo, Debian


> Unfortunately my favourite Linux distribution (SuSE)
> does not support the PPC platform anymore :(

SUSE has very good PPC support.
IBM even recommands SUSE and RedHat together with their big POWER-machines.
For PPC you need to use the SUSE Server version.


I have tried Yellow Dog on one of my MACs.
= the install was a piece of cake.

On my Pegasos ( www.pegasosppc.com ) I'm very happy with Debian.
The Pegasos is a really nice, geeky machine.
With a Pegasos you could release binaries for MorphOS as well. :-)


Kind regards

Gunnar

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



RE: fulltext search speed issue with SQL_CALC_FOUND_ROWS

2003-12-05 Thread Boehn, Gunnar von
Hi TK,


There was an optimizer bug in MySQL 4.0

This bug is fixed in 4.0.17 (not yet released)

# Fixed bug when the optimiser did not
# take SQL_CALC_FOUND_ROWS into account
# if LIMIT clause was present. (Bug #1274) 



Kind regards
Gunnar

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 4. Dezember 2003 16:13
> To: [EMAIL PROTECTED]
> Subject: fulltext search speed issue with SQL_CALC_FOUND_ROWS 
> 
> 
> I have some_table with 100,000 rows and with an
> average of 500 words in some_column of each row. When
> i do a fulltext search on this table using a query
> such as the following, all of my results are under 0.1
> seconds:
> 
> SELECT something
> FROM some_table
> WHERE MATCH (some_column) AGAINST ('some_search_term')
> LIMIT 0,10
> 
> However, when i add the SQL_CALC_FOUND_ROWS keyword
> like in the following query, some queries take longer
> than 1 minute:
> 
> SELECT SQL_CALC_FOUND_ROWS something
> FROM some_table
> WHERE MATCH (some_column) AGAINST ('some_search_term')
> LIMIT 0,10
> 
> How can there be a huge difference in speed if both
> queries always return the exact same results?
> 
> Thanks,
> TK

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



RE: MySQL 4.1.1 has been released

2003-12-04 Thread Boehn, Gunnar von
Hi Lenz,


Lenz Grimmer wrote:

> MySQL 4.1.1, a new version of the popular Open Source/Free Software
> database management system, has been released. It is now available in
> source and binary form for a number of platforms from our 
> download pages

Any chance to offer binaries for PowerPC Linux as well ? (Preferable tgz)



Thanks in advance

Gunnar

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



Feature wish

2003-11-18 Thread Boehn, Gunnar von
Hi,

I wonder if a small enhancement to the
mysql planner/optimizer could be made.


The current (mysql4.0) optimizer only uses one index per SELECT.
Because of this some queries result in a slow fulltable scan
even if all used columns are indexed.

Example:
SELECT * FROM table1 WHERE columnA='x' OR columnB='x'
(Slow table scan even if columnA and columnB are indexd!
 Other Databases like PostgreSQL don't have this problem.)


Since Mysql 4.0 a UNION can be used to speed this up.

Example: 
SELECT * FROM table1 WHERE columnA='x'
UNION SELECT * FROM table1 WHERE columnB='x'
(Now we have two SELECT with one index each.)


Couldn't the planner/optimizer be easely changed to do this UNION
automaticly ?


I think this would be a big improvement to mysql.

If I port applications from other databases to mysql
there are often queries like this. Either those queries
run terrible slow an mysql or I have to manually convert them into UNIONs.


Thanks in advance
Gunnar

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