To: mysql@lists.mysql.com
Subject: Re: Locking a Database (not tables) x
Hi David.
On 3/21/2014 1:42 PM, David Lerer wrote:
Frequently, we import a production dump that contains only 1 or 2 databases
into one of our QA instances that contains many more databases. (i.e.
database being a schema
...@oracle.com]
Sent: Friday, March 21, 2014 3:34 PM
To: mysql@lists.mysql.com
Subject: Re: Locking a Database (not tables) x
Hi David.
On 3/21/2014 1:42 PM, David Lerer wrote:
Frequently, we import a production dump that contains only 1 or 2 databases into one of our QA instances
that contains many more
2014-03-21 18:42 GMT+01:00 David Lerer dle...@univision.net:
Frequently, we import a production dump that contains only 1 or 2
databases into one of our QA instances that contains many more databases.
(i.e. database being a schema or a catalogue).
At the beginning of the import script, we
Perhaps enabling read only, followed by import with super user will do what you
want.
On Mar 22, 2014, at 12:26 AM, Manuel Arostegui man...@tuenti.com wrote:
2014-03-21 18:42 GMT+01:00 David Lerer dle...@univision.net:
Frequently, we import a production dump that contains only 1 or 2
Frequently, we import a production dump that contains only 1 or 2 databases
into one of our QA instances that contains many more databases. (i.e.
database being a schema or a catalogue).
At the beginning of the import script, we first drop all objects in the QA
database so that it will be a
Frequently, we import a production dump that contains only 1 or 2 databases
into one of our QA instances that contains many more databases. (i.e.
database being a schema or a catalogue).
At the beginning of the import script, we first drop all objects in the QA
database so that it will be a
: Friday, March 21, 2014 2:12 PM
To: David Lerer
Subject: Re: Locking a Database (not tables) x
You could set max_connections = 0; then kill off any remaining connections. Do
your data load and then set you max_connections back to what it was prior.
show variables like ‘max_connections’; (note
Hi David.
On 3/21/2014 1:42 PM, David Lerer wrote:
Frequently, we import a production dump that contains only 1 or 2 databases into one of our QA instances
that contains many more databases. (i.e. database being a schema or a
catalogue).
At the beginning of the import script, we first drop
