More queries yes but not more disk i/o. The first query will never touch
a disk.
[EMAIL PROTECTED] wrote:
Eric Bergen <[EMAIL PROTECTED]> wrote on 06/09/2005 12:56:59 PM:
How about something like this:
mysql> select @t := now();
+-+
| @t := now() |
+
Eric Bergen wrote:
How about something like this:
mysql> select @t := now();
+-+
| @t := now() |
+-+
| 2005-06-09 09:55:49 |
+-+
1 row in set (0.00 sec)
if the timestamp is not needed on the client with :
mysql> do @t := now(
Eric Bergen <[EMAIL PROTECTED]> wrote on 06/09/2005 12:56:59 PM:
> How about something like this:
> mysql> select @t := now();
> +-+
> | @t := now() |
> +-+
> | 2005-06-09 09:55:49 |
> +-+
> 1 row in set (0.00 sec)
> mysql> inse
How about something like this:
mysql> select @t := now();
+-+
| @t := now() |
+-+
| 2005-06-09 09:55:49 |
+-+
1 row in set (0.00 sec)
mysql> insert delayed into t set t = @t;
Query OK, 1 row affected (0.00 sec)
mysql> select *
On 6/9/05, Jeremiah Gowdy wrote:
> >
> > Does this seem to break SQL / application logic in some fashion?
>
> >Not worse then it is currently broken :)
> >
> >According to the SQL standard CURRENT_TIMESTAMP, which in MySQL is a
> >synonym for NOW(), is supposed to have a value that does not change
I am proposing that when a query is received by MySQL, a timestamp could
be taken immediately, and that timestamp could travel with the query until
it is actually processed. For delayed inserts, the query would still sit
in the insert queue, and it would still say NOW(), but when the query
fin
On 6/9/05, Jeremiah Gowdy wrote:
>
> I am proposing that when a query is received by MySQL, a timestamp could be
> taken immediately, and that timestamp could travel with the query until it is
> actually processed. For delayed inserts, the query would still sit in the
> insert queue, and it wo
- Original Message -
From: "Jeff Smelser" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 09, 2005 7:50 AM
Subject: Re: INSERT DELAYED and NOW()
On Thursday 09 June 2005 09:39 am, Jeremiah Gowdy wrote:
I am proposing that when a query is received by MySQL, a timestamp
On Thursday 09 June 2005 09:39 am, Jeremiah Gowdy wrote:
> I am proposing that when a query is received by MySQL, a timestamp could be
> taken immediately, and that timestamp could travel with the query until it
> is actually processed. For delayed inserts, the query would still sit in
> the inse
I'm wondering if anyone else has run into this issue.
We are logging from a real-time telecom application (we have callers on the
phone that are being handled by threads that are logging to MySQL), and because
of the nature of that application, we use INSERT DELAYED. There are multiple
compute
10 matches
Mail list logo
