Raj Shekhar writes:
> One option here might be to use "mysql proxy" as a man-in-the-middle and
> filter out unwanted queries...
This seems more or less the same as what I'm doing now with php.
The same question applies there - what would you look for in your
filter?
--
MySQL General Mailing Li
Daevid Vincent writes:
> > > For the love of God and all that is holy,
> > > do NOT put the user/pass on the URL like that!!
> > What's so unholy (or even unwise) about it?
> Oh my goodness, where to begin...
> Well barring the fact that it'll be in the user's cache and browser
It won't b
Daevid Vincent writes:
> For the love of God and all that is holy,
> do NOT put the user/pass on the URL like that!!
What's so unholy (or even unwise) about it?
> Or use "mod_auth_mysql" to maintain your 'authorized' users to your page.
Why is this so much better?
In my case it's worse ca
Adam Alkins writes:
> Sounds like you just want to GRANT access to specific tables (and with
> limited commands), which is exactly what MySQL's privilege system does.
How about this part?
> > Finally, suppose I want to limit access to the table to the rows
> > where col1=value1. If I just add
This seems like a topic that must have been studied, but I'm having
trouble figuring out what to search for in Google, since the usual
discussion of sql injection is not what I'm looking for here.
If anyone knows of references that discuss the issue, I'd like to
see them. I'm also interested in a
This is using version: 5.0.18-log on linux.
I have a stored procedure that takes .2 sec the first time,
12 the second, 12 the third. The data is unchanged.
The relevant part of the procedure looks like this.
...
drop temporary table if exists temptab;
create temporary table temptab (index (
Paul DuBois writes:
> At 17:26 -0700 10/6/03, Don Cohen wrote:
> >http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html
> >says
> >
> > you must retrieve all the rows even if you determine in
> > mid-retrieval that you've found the i
http://www.mysql.com/documentation/mysql/bychapter/manual_Clients.html
says
you must retrieve all the rows even if you determine in
mid-retrieval that you've found the information you were looking
for.
My question is: why?
In fact I thought that the normal interface for a database would sho
