A Newbie question about "make" and the term.c file

I am trying to install mysql 5.1.59 on my ppc running os x and I get this error message in the term.c file. cc1: warnings being treated as errors term.c: In function ‘term_set’: term.c:946: warning: passing argument 1 of ‘tgetflag’ discards qualifiers from pointer target type term.c:947: warning:

Re: MySQL anemic GIS support

Somebody feel to jump in and contradict me here, but I have never had any love from the MySQL GIS stack. For the very few functions it does support, the performance has been abysmal and I generally find myself hacking together UDFs against columns of FLOAT and avoiding POINT altogether. - md On

MySQL anemic GIS support

Anyone have any idea on if/when MySQL will get real GIS support? http://mysqldbnews.blogspot.com/2007/10/does-mysql-gis-make-grade.html …is what I'm referring to. Specifically, the factor that many functions are quietly replaced with MBRContains(). This makes it, for example, not possibl

Re: MySQL Indexes

At 01:58 PM 10/7/2011, you wrote: Do you have any good documentation with regards creating indexes. Also information for explain statement and what would be the desired result of the explain statement? This might help: http://dev.mysql.com/doc/refman/5.0/en/mysql-indexes.html http://www.site

Re: FW: MySQL Indexes

That cleared it up for me. Thanks! On 10/07/2011 03:06 PM, Jerry Schwartz wrote: -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Friday, October 07, 2011 12:21 PM To: mysql@lists.mysql.com Subject: Re: MySQL Indexes but could this not be called a bug? [JS

FW: MySQL Indexes

>-Original Message- >From: Reindl Harald [mailto:h.rei...@thelounge.net] >Sent: Friday, October 07, 2011 12:21 PM >To: mysql@lists.mysql.com >Subject: Re: MySQL Indexes > >but could this not be called a bug? > [JS] No. Think of two telephone books: one is sorted by first name, last name an

Re: MySQL Indexes

The second index you specified '(field_b, field_a)' would be usable when querying on field_b alone, or both fields in conjunction. This particular index is of no value should you be querying 'field_a' alone. Then that first index '(field_a, field_b)' would apply. - md On Fri, Oct 7, 2011 at 2:

Re: MySQL Indexes

Do you have any good documentation with regards creating indexes. Also information for explain statement and what would be the desired result of the explain statement? On 7 Oct 2011, at 17:10, Michael Dykman wrote: > How heavily a given table is queried does not directly affect the index size,

Re: MySQL Indexes

Can you give more information as to why the second index would be of no use ? On 7 Oct 2011, at 18:24, Michael Dykman wrote: > No, I don't think it can be called. It is a direct consequence of the > relational paradigm. Any implementation of an RDBMS has the same > characteristic. > > - md

Re: MySQL Indexes

No, I don't think it can be called. It is a direct consequence of the relational paradigm. Any implementation of an RDBMS has the same characteristic. - md On Fri, Oct 7, 2011 at 12:20 PM, Reindl Harald wrote: > but could this not be called a bug? > > Am 07.10.2011 18:08, schrieb Michael Dykm

Re: MySQL Indexes

but could this not be called a bug? Am 07.10.2011 18:08, schrieb Michael Dykman: > When a query selects on field_a and field_b, that index can be used. If > querying on field_a alone, the index again is useful. Query on field_b > alone however, that first index is of no use to you. > > On Fri,

Re: MySQL Indexes

How heavily a given table is queried does not directly affect the index size, only the number and depth of the indexes. No, it is not that unusual to have the index file bigger. Just make sure that every index you have is justified by the queries you are making against the table. - md On Fri,

Re: MySQL Indexes

When a query selects on field_a and field_b, that index can be used. If querying on field_a alone, the index again is useful. Query on field_b alone however, that first index is of no use to you. On Fri, Oct 7, 2011 at 10:49 AM, Brandon Phelps wrote: > This thread has sparked my interest. What

Re: MySQL Indexes

This thread has sparked my interest. What is the difference between an index on (field_a, field_b) and an index on (field_b, field_a)? On 10/06/2011 07:43 PM, Nuno Tavares wrote: Neil, whenever you see multiple fields you'd like to index, you should consider, at least: * The frequency of each

RE: How MyISAM handle auto_increment

>-Original Message- >From: Lucio Chiappetti [mailto:lu...@lambrate.inaf.it] >Sent: Thursday, October 06, 2011 3:18 AM >To: Jerry Schwartz >Cc: Mysql List >Subject: RE: How MyISAM handle auto_increment > >On Wed, 5 Oct 2011, Jerry Schwartz wrote: > >> Can't you use >> CREATE TABLE LIKE

Re: 4 minute slow on select count(*) from table - myisam type

Good to see the issue has been solved. What I noticed in the mysqltuner output, is that you may want to enlarge your table_cache and open files limit before you run into problems there. - Original Message - > From: "Johnny Withers" > > I haven't used MYISAM in a long time, so i'm not s

Re: mysqldiff resurrected and 0.43 released

Looks very nice, Ill check it out next week. Thanks for the work! -- Rik Wasmus > After a very long hiatus from maintainership (several years), I have > finally released a new version of MySQL-Diff, the CPAN module suite > which also contains mysqldiff, a CLI-based frontend tool for comparing > t

Re: MySQL Indexes

Is it normal practice for a heavily queried MYSQL tables to have a index file bigger than the data file ? On Fri, Oct 7, 2011 at 12:22 AM, Michael Dykman wrote: > Only one index at a time can be used per query, so neither strategy is > optimal. You need at look at the queries you intend to run