SP generally goes as per the database you have created. Set you binlog off
while creating for the sql.
sql_log_bin is the variable to do it.
On Tue, Jun 8, 2010 at 1:01 AM, Sabika Gmail <sabika.makhdoom@stripped>wrote:
> I already have mysql in the replicate wild ingore table. I am running mysql
> Could it be a bug?
> On Jun 7, 2010, at 8:30 AM, Rolando Edwards <redwards@stripped>
> I think this is normal because stored procedures live in mysql.proc.
>> You would have to filter out mysql.proc by adding this to /etc/my.cnf
>> Rolando A. Edwards
>> MySQL DBA (CMDBA)
>> 155 Avenue of the Americas, Fifth Floor
>> New York, NY 10013
>> 212-625-5307 (Work)
>> 201-660-3221 (Cell)
>> AIM & Skype : RolandoLogicWorx
>> -----Original Message-----
>> From: Sabika Gmail [mailto:sabika.makhdoom@stripped]
>> Sent: Monday, June 07, 2010 11:14 AM
>> To: mysql@stripped
>> Subject: Replication of MySQL Stored Procedure
>> I have a database in the wild ignore table as table.%. Recently I
>> created a store procedure on it and it replicated. Does any one know
>> if this is normal bahvior? If I wanted to make sure store procedures
>> do not replicate, what should I do?
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe:
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: