I haven't bothered to look for the bug, but it seems to me to be quite
reasonable default behaviour to lock the whole lot when you're dumping
transactional tables - it ensures you dump all tables from the same consistent
view.
I would rather take this up with the ZRM people - it should just
On Mon, 06 Jun 2011 12:44 +0200, Johan De Meersman
vegiv...@tuxera.be wrote:
I haven't bothered to look for the bug, but it seems to me to be quite
reasonable default behaviour to lock the whole lot when you're dumping
transactional tables - it ensures you dump all tables from the same
When you UPDATE a record, a timestamp field (`t`) is set to the current time
in the time zone given by @@time_zone, correct? That will usually be the local
time.
If somebody in another time zone needs to compare `t` against //their own//
local time, they need to use
- Original Message -
From: ag...@airpost.net
Excluding 'performance_schema' appears to eliminate the error. And it
seems does NOT cause a reliability-of-the-backup problem.
Hah, no, backing that up is utterly pointless. Never noticed it doing that.
It's basically a virtual schema
I may be mistaken, but isn't UTC pretty much GMT if you don't want subsecond
precision? Set your server's timezone to GMT and you should get what you want.
- Original Message -
From: Jerry Schwartz je...@gii.co.jp
To: mysql@lists.mysql.com
Sent: Monday, 6 June, 2011 5:10:22 PM
-Original Message-
From: Johan De Meersman [mailto:vegiv...@tuxera.be]
Sent: Monday, June 06, 2011 12:57 PM
To: Jerry Schwartz
Cc: mysql@lists.mysql.com
Subject: Re: Timestamp value
I may be mistaken, but isn't UTC pretty much GMT if you don't want subsecond
precision? Set your server's
On Mon, 06 Jun 2011 18:54 +0200, Johan De Meersman
vegiv...@tuxera.be wrote:
Excluding 'performance_schema' appears to eliminate the error. And it
seems does NOT cause a reliability-of-the-backup problem.
Hah, no, backing that up is utterly pointless.
that's a useful/final confirmation.
I am trying to optimize a query that uses a group by on a varchar(255)
column. The column has a large enough cardinality that a 10 character
partial index uniquely covers over 99% of all values. I was hoping
that this partial index would be able to help with the group by
(though obviously not as
Hopefully I won't look like too much of a numbskull here but after
reading some sites on table optimization, I decided to remove the NULL as
default on the fields in my products table. I thought everything went well
until I realized that we hadn't received any orders for 2 days.
- Original Message -
From: sono...@fannullone.us
description? Why would removing the NULL default cause data to be
lost?
What exactly do you mean by removing the NULL default? Did you set your
colums NOT NULL?
--
Bier met grenadyn
Is als mosterd by den wyn
Sy die't
10 matches
Mail list logo