From: Mohammed Abdul Azeem Sent: 13 April 2006 07:29
>
> Hi
>
> Iam having a problem using "select into outfile" command, iam getting
> the following error. can anyone help me trace the problem.
>
> mysql> SELECT * INTO OUTFILE'/home/public1/data.txt' FROM temp_table
> WHERE last_time_update =
Matt Babineau wrote:
> Ok I installed PHP 4.3.10 and it still has not fixed the problem. If I
> remove the SQL_CALC_FOUND_ROWS from the query, it works no problems! This
> is
> very strange behavior!
Not really that strange, I think...
While you might want to read this:
http://us4.php.net/manual
A quick look at the PHP site...
http://www.php.net/manual/en/faq.databases.php#faq.databases.upgraded
Regards, Jigal.
- Original Message -
From: "Matt Babineau" <[EMAIL PROTECTED]>
To: "'MySQL General'"
Sent: Tuesday, February 01, 2005 9:20 PM
Subject: Problem with SELECT SQL_CALC_FOUN
: Michael Stassen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 3:55 PM
To: Michael Dykman
Cc: Matt Babineau; 'MySQL General'
Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS
I'm confused. That bug was closed over 2 years ago. What makes you think
it applies here, and
e
what happens?
Matt Babineau
Criticalcode
w: http://www.criticalcode.com
p: 858.733.0160
e: [EMAIL PROTECTED]
-Original Message-
From: Michael Dykman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 12:47 PM
To: Matt Babineau
Cc: 'MySQL General'
Subject: Re: Problem with SE
al Message-
> From: Michael Dykman [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 01, 2005 12:47 PM
> To: Matt Babineau
> Cc: 'MySQL General'
> Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS
>
> Matt,
>
> I suspect your problem is PHP, not My
-
From: Matt Babineau [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 12:52 PM
To: 'Michael Dykman'
Cc: 'MySQL General'
Subject: RE: Problem with SELECT SQL_CALC_FOUND_ROWS
Weird thing is that I am running PHP 4.3.9I guess I can upgrade and see
what happ
:47 PM
To: Matt Babineau
Cc: 'MySQL General'
Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS
Matt,
I suspect your problem is PHP, not MySQL. refer to
http://bugs.php.net/bug.php?id=16906&edit=1
On Tue, 2005-02-01 at 15:20, Matt Babineau wrote:
> Hi All-
>
&
Matt,
I suspect your problem is PHP, not MySQL. refer to
http://bugs.php.net/bug.php?id=16906&edit=1
On Tue, 2005-02-01 at 15:20, Matt Babineau wrote:
> Hi All-
>
> I'm running a query that uses SQL_CALC_FOUND_ROWS for my search engine on a
> real estate site. The problem is that I get
ry(); statement.
Matt Babineau
Criticalcode
w: http://www.criticalcode.com <http://www.criticalcode.com/>
p: 858.733.0160
e: [EMAIL PROTECTED]
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 12:25 PM
To: Matt Babineau
Cc: 'MySQL
"Matt Babineau" <[EMAIL PROTECTED]> wrote on 02/01/2005 03:20:49 PM:
> Hi All-
>
> I'm running a query that uses SQL_CALC_FOUND_ROWS for my search engine
on a
> real estate site. The problem is that I get an error when I run my
query:
>
> "Warning mysql_query(): Unable to save result set in
/
Muazzam Siddiqui wrote:
Hi,
I am getting the error
You have an error in your SQL syntax near 'select max(news_id) from
news)' at line 1
while trying to run this query.
SELECT * FROM News where News_ID = (SELECT MAX(News_ID) FROM News);
You don't say what version of MySQL you are running.
You
This is what happens when you use LIMIT
MySQL retrieves the entire record set for the select and then sends the
number requested in the LIMIT parameter to the client. MySQL has to
retrieve the entire result set to accommodate a LIMIT clause which skips
n records i.e. LIMIT 250,10.
With no ORDER B
On Wed, 23 Oct 2002 19:15:59 +0300
"Andrey Hristov" <[EMAIL PROTECTED]> wrote:
> I am not an expert but I think that when there is not order by the
> output is sorted on the primary key.
> So : select * from log_answers_index limit 0,10 and select * from
> log_ansers_index where log_entry_id be
wrote:
- Original Message -
From: "gerald_clark" <[EMAIL PROTECTED]>
To: "Andrey Hristov" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, October 23, 2002 6:23 PM
Subject: Re: Problem with select.
Andrey Hristov wrote:
HI,
I
- Original Message -
From: "gerald_clark" <[EMAIL PROTECTED]>
To: "Andrey Hristov" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, October 23, 2002 6:23 PM
Subject: Re: Problem with select.
>
>
> Andrey Hristov wrote:
>
Andrey Hristov wrote:
HI,
I don't know is it bad or not but I face queries the work quite long time.
the sql is :
select * from log_answers_index limit 0,10
and it takes too much time for me to receive the result.
I got indexes on most of the fields, i got primary key which is
auto_increment
On Thu, 02 May 2002 13:11:23 +0400
"Sheni R. Meledath" <[EMAIL PROTECTED]> wrote:
> Using the second command I can't display all the records.
>
> But using separate select statement I can select & display any record which
> is not displayed in the above case.
> ###
> $result=mysql_query("selec
Many Thanks for your quick reply.
The MySQL version is 3.22 on Unix/FreeBSD/Apache.
thanks
At 08:43 AM 5/2/02 -0500, Gerald Clark wrote:
>Unfortunately, you did not tell us what version you are running, or what
>platform you are running it on.
>
>
>Try rebuilding the indexes with myisamchk or
Unfortunately, you did not tell us what version you are running, or what
platform you are running it on.
Try rebuilding the indexes with myisamchk or whatever is appropriate for
your table type.
Sheni R. Meledath wrote:
> Hello:
>
> I have a problem while selecting the records from a table.
Hi!
It is a bug in the parser that it does not accept ... IN SHARE MODE
immediately after a WHERE clause. I think yacc is not very sophisticated
in lookahead of symbols when it is trying to parse a statement, and may
confuse IN SHARE MODE to WHERE colA IN ().
We will fix the parser, but mean
21 matches
Mail list logo
