From: Rick James
Date: September 24 2012 5:03pm
Subject: RE: How to block SELECT * FROM table; but not SELECT * FROMT table
 WHERE...;
List-Archive: http://lists.mysql.com/mysql/228250
Message-Id: <2E7DD7ADE53B044C8C8BCD9C5829E1EB148CF919BB@SP2-EX07VS01.ds.corp.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Even if you could block them, they would be easy to get around:
  SELECT * FROM tbl WHERE 1;

If you have long running queries, you should investigate the reasons (other=
 than lack of WHERE).

* MyISAM locks the table for any writes.  This prevents a SELECT from start=
ing or a select can prevent the INSERT/UPDATE/DELETE from starting.  Consid=
er switching to InnoDB.

* How big is the table?  Why does the user want the whole table (if it is a=
 plain SELECT *)?  If you are doing Data Warehousing, consider summary tabl=
es.

Let's see the big picture; I expect there is a way to solve the _real_ prob=
lem, which I guess is "performance".

> -----Original Message-----
> From: Arthur Fuller [mailto:fuller.artful@stripped]
> Sent: Sunday, September 23, 2012 3:39 PM
> To: Tim Pownall
> Cc: mysql@stripped
> Subject: Re: How to block SELECT * FROM table; but not SELECT * FROMT
> table WHERE...;
>=20
> Tim,
>=20
> I think you misunderstood the question. Daniel wants to block Select
> queries that ask for all rwows, and permit only queries that ask for
> some rows, as restricted by the Where clause.
>=20
> Unfortunately, I don't think that can be done. But I'm not certain of
> that; there might be a trick.
>=20
> Arthur
> www.artfulsoftware.com
>=20
> On Sun, Sep 23, 2012 at 3:50 PM, Tim Pownall <pownalltim@stripped>
> wrote:
>=20
> >  select * from table where column=3Dvalue means it will return only
> rows
> > that match.  as long as you have proper indexing there should not be
> any issues.
> >
> > On Sun, Sep 23, 2012 at 1:23 PM, Luis Daniel Lucio Quiroz <
> > luis.daniel.lucio@stripped> wrote:
> >
> >