Jeremy Zawodny wrote:
> On Wed, Nov 14, 2001 at 12:07:04PM -0800, Bill Adams wrote:
> > The most important exception is the mysql_use_result attribute: This
> > forces the driver to use mysql_use_result rather than
> > mysql_store_result. The former is faster and less memory consuming,
> > but te
On Wed, Nov 14, 2001 at 12:07:04PM -0800, Bill Adams wrote:
> Man I just cannot stop replying to myself...
I've had days like that, too.
>
> The most important exception is the mysql_use_result attribute: This
> forces the driver to use mysql_use_result rather than
> mysql_store_result. The form
again Rick.
b.
> > > -----Original Message-
> > > From: Bill Adams [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, November 14, 2001 11:38 AM
> > > To: Mysql List
> > > Subject: Non-Buffered mysqld
> > >
> > > MySQL 4.0
> >
]buffered'.)
I do not see anything for DBD::mysql (anyone?)
Is there a general option or a query that can be run to have the same effect?
b.
> > -Original Message-
> > From: Bill Adams [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, November 14, 2001 11:38 AM
> &g
ile the query is running w/o any results being returned yet, the process
list shows "sending data".
b.
>
>
> -Original Message-
> From: Bill Adams [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 14, 2001 11:38 AM
> To: Mysql List
> Subject: Non-Bu
If you use PHP, the answer is:mysql_unbuffered_query()
-Original Message-
From: Bill Adams [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 14, 2001 11:38 AM
To: Mysql List
Subject: Non-Buffered mysqld
MySQL 4.0
Is there a way to prevent mysql(d) from buffering
the output ala
MySQL 4.0
Is there a way to prevent mysql(d) from buffering
the output ala 'mysqldump -q'?
The specific case I am thinking of is a simple
SELECT ... FROM ... WHERE (with no ORDER BY, no
GROUP BY, etc.). In this case there is no reason
[that I can think of] why mysqld cannot start
returning reco
