From: Jeff Smelser
Date: June 9 2005 2:50pm
Subject: Re: INSERT DELAYED and NOW()
List-Archive: http://lists.mysql.com/mysql/185251
Message-Id: <200506090950.51147.tradergt@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart5842879.vZcQoZvBRN";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart5842879.vZcQoZvBRN
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 insert queue, and it would still say NOW(), but when the query finally
> gets executed, NOW() is evaluated simply by returning the timestamp of wh=
en
> the query was received, rather than when it was processed.

Why cant you use the application to do a timestamp.. so when you send the=20
insert, it send with the timestamp of when the query would have actually be=
en=20
inserted?

Jeff

--nextPart5842879.vZcQoZvBRN
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCqFdLoOk9EvUvEtgRAhUTAKDnOG3m6S7RFIl6/E+a2Fg8JhuPYgCfSbaN
KERdsf39yBiLtQ/rF5jBxMs=
=gbTG
-----END PGP SIGNATURE-----

--nextPart5842879.vZcQoZvBRN--