RE: Regarding storing non-english chars in mysql

[Ningappa Koneri]

Solved... :)

What I did is:
1.I changed the selected columns charset to utf8 but other columns, table and 
database where using default charset.
2.Before doing a simple insert of parameters received from browser into mysql, 
I executed "set names 'utf8'" on the same connection and again while selecting 
as well.
3.It worked even after removing  tag from the head tag as well <-- plz 
through some light y it got displayed at the browser ?


@fsb thanks a lot for ur valuable i/p
@Gavin I wrote my stub refering to that link only cheers!

Regards,
Ningappa Koneri
mLifestyle | www.comviva.com



-Original Message-
From: fsb [mailto:f...@thefsb.org]
Sent: Tuesday, January 19, 2010 2:35 AM
To: Ningappa Koneri; mysql@lists.mysql.com
Subject: Re: Regarding storing non-english chars in mysql

you can specify the character encoding (called CHARSET in mysql) and
collation on a per column, per table or per database level. e.g.

CREATE DATABASE foo CHARACTER SET utf8 COLLATE utf8_general_ci;

or

CREATE TABLE foo ( ... ) CHARACTER SET utf8 COLLATE utf8_general_ci;

or

CREATE TABLE foo (
bar varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL);

mysql's default character encoding is latin1.

for mysql's collations, see: http://www.collation-charts.org/

i wouldn't use utf8 indiscriminately, only for columns that need it --
indexes need 3 bytes per character on utf8 columns. (utf16 would be better
in that regard!)

don't forget to set session system variables, e.g. using SET NAMES or with
your api.


On 1/18/10 2:44 PM, "Gavin Towey"  wrote:

> http://dev.mysql.com/doc/refman/5.0/en/charset.html
>
>
> -Original Message-
> From: Ningappa Koneri [mailto:ningappa.kon...@comviva.com]
> Sent: Sunday, January 17, 2010 11:32 PM
> To: mysql@lists.mysql.com
> Subject: Regarding storing non-english chars in mysql
>
> Dear all,
>
> I have a problem in migrating a GUI app(displays multi lingual data like
> Arabic) which currently uses oracle as backend db to mysql (5.1). Currenly in
> oracle I am using NVARCHAR datatype to store the Arabic chars. How do I
> incorporate the same functionality in mysql ? I have tried a sample
> servlet/jsp to insert the arabic chars into mysql by creating a table having
> two columns of NATIONAL VARCHAR type, but it's not displaying Arabic chars
> instead only questions marks are there.
>
> One more thing in sample example is that before inserting I am converting to
> UTF-8.
>
> Regards,
> Ningappa Koneri
> mLifestyle | www.comviva.com
>
>
> This e-mail and all material transmitted with it are for the use of the
> intended recipient(s) ONLY and contains confidential and/or privileged
> information. If you are not the intended recipient, please contact the sender
> by reply e-mail and destroy all copies and the original message. Any
> unauthorized review, use, disclosure, dissemination, forwarding, printing or
> copying of this email or any action taken pursuant to the contents of the
> present e-mail is strictly prohibited and is unlawful.
> The recipient acknowledges that Comviva Technologies Limited or its management
> or directors, are unable to exercise control or ensure the integrity over /of
> the contents of the information contained in e-mail. Any views expressed
> herein are those of the individual sender only and no binding nature of the
> contents shall be implied or assumed unless the sender does so expressly with
> due authority of Comviva Technologies Limited. E-mail and any contents
> transmitted with it are prone to viruses and related defects despite all
> efforts to avoid such by Comviva Technologies Limited.
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql?unsub=gto...@ffn.com
>
>
> This message contains confidential information and is intended only for the
> individual named.  If you are not the named addressee, you are notified that
> reviewing, disseminating, disclosing, copying or distributing this e-mail is
> strictly prohibited.  Please notify the sender immediately by e-mail if you
> have received this e-mail by mistake and delete this e-mail from your system.
> E-mail transmission cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. The sender therefore does not accept liability
> for any loss or damage caused by viruses or errors or omissions in the
> contents of this message, which arise as a result of e-mail transmission.
> [FriendFinder Networks, Inc., 220 Humbolt court, Sunnyvale, CA 94089, USA,
> FriendFinder.com
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql?unsub=...@thefsb.org
>



This e-mail and all material transmitted with it are for the use of the 
intended recipient(s) ONLY and contains confidential and/or privileged 
information. If you are not the 

Re: MySQL Replication Delete is not gettting replicated

[Suresh Kuna]

Hi Manasi,
That alone is the difference in this case.

-- 
Thanks
Suresh Kuna
MySQL DBA

On Tue, Jan 19, 2010 at 10:36 AM, Manasi Save <
manasi.s...@artificialmachines.com> wrote:

> Dear Carlos,
>
> Thanks for the response. But I haven't gave any privileges besides
> repl_slave priv to user replication and replication2 respectively.
> So does that amke any difference really?
>
>
> Thanks in advance.
> --
> Regards,
> Manasi Save
>
> Quoting Carlos Proal :
>
>>
>> I dont see anything unusual or missing on your config file and as the
>> only thing missing are deletes, i think that might be a permission issue.
>> Can you check out the grants for your replication users and see if they
>> have full permissions granted ?
>>
>> mysql> show grants for x;
>>
>> where is x is replication and replication2 respectively.
>> Carlos
>>
>>
>> On 1/18/2010 1:35 AM, Manasi Save wrote:
>> > Hi Anand,
>> >
>> > Please find below my configuration file of both the masters:
>> >
>> > ON MASTER 1:
>> >
>> > [mysqld]
>> > datadir=/var/lib/mysql/
>> > socket=/var/lib/mysql/mysql.sock
>> > old_passwords=1
>> >
>> > log-bin=/usr/local/mysql/bin.log
>> > #binlog-do-db=  # input the database which should
>> > be replicated
>> > binlog-ignore-db=mysql# input the database that should be
>> > ignored for replication
>> > binlog-ignore-db=test
>> > log-bin-index=/usr/local/mysql/log-bin.index
>> > log_slave_updates
>> >
>> > server-id=2
>> >
>> > auto_increment_increment=2
>> > auto_increment_offset=1
>> >
>> > #information for becoming slave. > master-host = 192.168.1.1
>> > master-user = replication
>> > master-password = replication
>> > master-port = 3306
>> >
>> > [mysql.server]
>> > user=mysql
>> >
>> > [mysqld_safe]
>> > err-log=/var/lib/mysql/mysql.log
>> > pid-file=/var/lib/mysql/mysql.privatedns.com.pid
>> >
>> > ON MASTER 2:
>> >
>> > [mysqld]
>> > datadir=/var/lib/mysql/
>> > socket=/var/lib/mysql/mysql.sock
>> > old_passwords=1
>> >
>> > log-bin=/usr/local/mysql/bin.log
>> > #binlog-do-db=  # input the database which should
>> > be replicated
>> > binlog-ignore-db=mysql# input the database that should be
>> > ignored for replication
>> > binlog-ignore-db=test
>> > log-bin-index=/usr/local/mysql/log-bin.index
>> > log_slave_updates
>> >
>> > server-id=1
>> >
>> > auto_increment_increment=2
>> > auto_increment_offset=2
>> >
>> > #information for becoming slave. > master-host = 192.168.1.2
>> > master-user = replication2
>> > master-password = replication2
>> > master-port = 3306
>> >
>> > [mysql.server]
>> > user=mysql
>> >
>> > [mysqld_safe]
>> > err-log=/var/var/lib/mysql/mysql.log
>> > pid-file=/var/lib/mysql/mysql.privatedns.com.pid
>> >
>> > Please let me know if I need to add any parameter to enable this
>> > replication. >
>> > Thanks in advance. >
>> > --
>> >
>> > Regards,
>> >
>> > Manasi Save
>> >
>> >
>> >
>> > Quoting Anand kumar :
>> >
>> > can you give us the configuration(.cnf) file from both the masters ?
>> > --Anand
>> > On Sat, Jan 16, 2010 at 3:06 PM, Manasi Save
>> > > > > wrote:
>> >
>> > Hi All,
>> >
>> >
>> > I have configured MySQL Master-Master Replication on my
>> > servers. When I am inserting or updating any data in a regular
>> > table the data is getting replicated. >
>> >
>> > But When I am doing delete on that same table. the data is
>> > only getting deleted only on the server where I am doing
>> > delete. but it is not getting replicated on its slave. >
>> >
>> > Even if I am doing truncate it is not getting replicated. Can
>> > anyone provide any input on this?
>> >
>> >
>> > Thanks in advance. >
>> >
>> > --
>> >
>> > Regards,
>> >
>> > Manasi Save
>> >
>> >
>>
>>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=sureshkumar...@gmail.com
>
>

Re: MySQL Replication Delete is not gettting replicated

[Carlos Proal]

Hi Manasi

Yes, you only need the repl_slave_priv,  the show grants should give you 
something like:
GRANT REPLICATION SLAVE ON *.* TO 'replication'@'%' IDENTIFIED BY 
PASSWORD '...'


If thats ok, have check your binlog and relay binlog to see if them 
contain the delete statements?

Im trying to figure out whats wrong.

Carlos

On 1/18/2010 11:06 PM, Manasi Save wrote:

Dear Carlos,

Thanks for the response. But I haven't gave any privileges besides 
repl_slave priv to user replication and replication2 respectively.

So does that amke any difference really?

Thanks in advance.
--
Regards,
Manasi Save

Quoting Carlos Proal :


I dont see anything unusual or missing on your config file and as the
only thing missing are deletes, i think that might be a permission 
issue.

Can you check out the grants for your replication users and see if they
have full permissions granted ?

mysql> show grants for x;

where is x is replication and replication2 respectively.
Carlos


On 1/18/2010 1:35 AM, Manasi Save wrote:
> Hi Anand,
>
> Please find below my configuration file of both the masters:
>
> ON MASTER 1:
>
> [mysqld]
> datadir=/var/lib/mysql/
> socket=/var/lib/mysql/mysql.sock
> old_passwords=1
>
> log-bin=/usr/local/mysql/bin.log
> #binlog-do-db=  # input the database which should
> be replicated
> binlog-ignore-db=mysql# input the database that should be
> ignored for replication
> binlog-ignore-db=test
> log-bin-index=/usr/local/mysql/log-bin.index
> log_slave_updates
>
> server-id=2
>
> auto_increment_increment=2
> auto_increment_offset=1
>
> #information for becoming slave. > master-host = 192.168.1.1
> master-user = replication
> master-password = replication
> master-port = 3306
>
> [mysql.server]
> user=mysql
>
> [mysqld_safe]
> err-log=/var/lib/mysql/mysql.log
> pid-file=/var/lib/mysql/mysql.privatedns.com.pid
>
> ON MASTER 2:
>
> [mysqld]
> datadir=/var/lib/mysql/
> socket=/var/lib/mysql/mysql.sock
> old_passwords=1
>
> log-bin=/usr/local/mysql/bin.log
> #binlog-do-db=  # input the database which should
> be replicated
> binlog-ignore-db=mysql# input the database that should be
> ignored for replication
> binlog-ignore-db=test
> log-bin-index=/usr/local/mysql/log-bin.index
> log_slave_updates
>
> server-id=1
>
> auto_increment_increment=2
> auto_increment_offset=2
>
> #information for becoming slave. > master-host = 192.168.1.2
> master-user = replication2
> master-password = replication2
> master-port = 3306
>
> [mysql.server]
> user=mysql
>
> [mysqld_safe]
> err-log=/var/var/lib/mysql/mysql.log
> pid-file=/var/lib/mysql/mysql.privatedns.com.pid
>
> Please let me know if I need to add any parameter to enable this
> replication. >
> Thanks in advance. >
> --
>
> Regards,
>
> Manasi Save
>
>
>
> Quoting Anand kumar :
>
> can you give us the configuration(.cnf) file from both the 
masters ?

> --Anand
> On Sat, Jan 16, 2010 at 3:06 PM, Manasi Save
>  > wrote:
>
> Hi All,
>
>
> I have configured MySQL Master-Master Replication on my
> servers. When I am inserting or updating any data in a regular
> table the data is getting replicated. >
>
> But When I am doing delete on that same table. the data is
> only getting deleted only on the server where I am doing
> delete. but it is not getting replicated on its slave. >
>
> Even if I am doing truncate it is not getting replicated. Can
> anyone provide any input on this?
>
>
> Thanks in advance. >
>
> --
>
> Regards,
>
> Manasi Save
>
>







--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: MySQL Replication Delete is not gettting replicated

[Manasi Save]

Dear Carlos,

Thanks for the response. But I haven't gave any privileges besides 
repl_slave priv to user replication and replication2 respectively. 


So does that amke any difference really?

Thanks in advance. 


--
Regards,
Manasi Save

Quoting Carlos Proal :


I dont see anything unusual or missing on your config file and as the
only thing missing are deletes, i think that might be a permission issue. 


Can you check out the grants for your replication users and see if they
have full permissions granted ?

mysql> show grants for x;

where is x is replication and replication2 respectively. 


Carlos


On 1/18/2010 1:35 AM, Manasi Save wrote:
> Hi Anand,
>
> Please find below my configuration file of both the masters:
>
> ON MASTER 1:
>
> [mysqld]
> datadir=/var/lib/mysql/
> socket=/var/lib/mysql/mysql.sock
> old_passwords=1
>
> log-bin=/usr/local/mysql/bin.log
> #binlog-do-db=  # input the database which should
> be replicated
> binlog-ignore-db=mysql# input the database that should be
> ignored for replication
> binlog-ignore-db=test
> log-bin-index=/usr/local/mysql/log-bin.index
> log_slave_updates
>
> server-id=2
>
> auto_increment_increment=2
> auto_increment_offset=1
>
> #information for becoming slave. 
> master-host = 192.168.1.1

> master-user = replication
> master-password = replication
> master-port = 3306
>
> [mysql.server]
> user=mysql
>
> [mysqld_safe]
> err-log=/var/lib/mysql/mysql.log
> pid-file=/var/lib/mysql/mysql.privatedns.com.pid
>
> ON MASTER 2:
>
> [mysqld]
> datadir=/var/lib/mysql/
> socket=/var/lib/mysql/mysql.sock
> old_passwords=1
>
> log-bin=/usr/local/mysql/bin.log
> #binlog-do-db=  # input the database which should
> be replicated
> binlog-ignore-db=mysql# input the database that should be
> ignored for replication
> binlog-ignore-db=test
> log-bin-index=/usr/local/mysql/log-bin.index
> log_slave_updates
>
> server-id=1
>
> auto_increment_increment=2
> auto_increment_offset=2
>
> #information for becoming slave. 
> master-host = 192.168.1.2

> master-user = replication2
> master-password = replication2
> master-port = 3306
>
> [mysql.server]
> user=mysql
>
> [mysqld_safe]
> err-log=/var/var/lib/mysql/mysql.log
> pid-file=/var/lib/mysql/mysql.privatedns.com.pid
>
> Please let me know if I need to add any parameter to enable this
> replication. 
>
> Thanks in advance. 
>

> --
>
> Regards,
>
> Manasi Save
>
>
>
> Quoting Anand kumar :
>
> can you give us the configuration(.cnf) file from both the masters ?
> --Anand
> On Sat, Jan 16, 2010 at 3:06 PM, Manasi Save
>  > wrote:
>
> Hi All,
>
>
> I have configured MySQL Master-Master Replication on my
> servers. When I am inserting or updating any data in a regular
> table the data is getting replicated. 
>

>
> But When I am doing delete on that same table. the data is
> only getting deleted only on the server where I am doing
> delete. but it is not getting replicated on its slave. 
>

>
> Even if I am doing truncate it is not getting replicated. Can
> anyone provide any input on this?
>
>
> Thanks in advance. 
>

>
> --
>
> Regards,
>
> Manasi Save
>
>




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: mysqlpp::Connection memory leak?

[Attila]

I just noticed that the MySql Client library version that the server reports
is 5.1.11

Thanks again,

On Mon, Jan 18, 2010 at 9:22 PM, Attila  wrote:

> Hi Everyone,
>
> I have an application that uses a custom made DBConnectionPool.
> The architecture is basically as follows:
>
> All of the components (DBConnectionPool and DBWorker) run in their own
> strands (all work is queued, so no explicit locking is required), that
> is...  all work is run via threadpool threads.
>
> DBConnectionPool passes out connections.
> DBWorker's accept work (in the form of adding DBWork to it's list to
> process when a connection is received)
>   --> These DBWorkers will request a connection from the pool, the pool
> then queues a connection for usage back to the DBWorker (when a connection
> becomes available)
>
> That all being said, I am using the thread aware libraries of mysql and
> mysqlpp.
>
> Here are a couple of stack traces I get on application shutdown from a
> memory leak detector (using VLD 1.0 on VS 9.0):
>
> Connect related:
>
>   Call Stack:
> f:\dd\vctools\crt_bld\self_x86\crt\src\dbgmalloc.c (56): malloc
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\my_once.c
> (61): my_once_alloc
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\charset.c
> (62): init_state_maps
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\charset.c
> (435): init_available_charsets
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\charset.c
> (577): get_charset_by_csname
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\sql-common\client.c
> (1780): mysql_init_character_set
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\sql-common\client.c
> (2177): mysql_real_connect
> c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\dbdriver.cpp (89):
> mysqlpp::DBDriver::connect
> c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\connection.cpp (98):
> mysqlpp::Connection::connect
> c:\p4\dev\aa1\libs\toolsdatabase\mysqlppconnection.cpp (52):
> db::MySQLppConnection::MySQLppConnection
> c:\p4\dev\aa1\rstsrc\libs\toolsdatabase\mysqlppconnectionfactory.cpp
> (41): db::MySQLppConnectionFactory::CreateDBConnection
> (...omitted)
>
> I also get a store-related memory leak:
>
>  Call Stack:
> f:\dd\vctools\crt_bld\self_x86\crt\src\dbgmalloc.c (56): malloc
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\dbug\dbug.c
> (2022): DbugMalloc
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\dbug\dbug.c
> (345): code_state
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\dbug\dbug.c
> (967): _db_enter_
>
> g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\sql-common\client.c
> (2837): mysql_real_query
> c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\dbdriver.h (199):
> mysqlpp::DBDriver::execute
> c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\query.cpp (481):
> mysqlpp::Query::store
> c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\query.cpp (472):
> mysqlpp::Query::store
> c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\include\query.h (467):
> mysqlpp::Query::store
> c:\p4\dev\aa1\libs\toolsdatabase\mysqlppconnection.cpp (212):
> db::MySQLppConnection::SelectExec
> (...omitted)
>
>
> I know that I am cleaning up my wrapper objects correctly.
> MySQLppConnection has an auto_ptr to mysqlpp::Connection and I know the
> destructors are being called.
>
> Versions I am using:
>
> mysqlpp:  3.0.8
> mysql:  5.1.30
> Running mysql server instance: 5.1.41
>
>
> Questions:
>
> Is my combination of versions incorrect?
> Should I be using the mysql-c libraries for the same version as the running
> server instance?
> If I am passing a mysqlpp::Connection object around to different objects
> (in different threads) -- could it cause a memory leak or other problems? (I
> can guarantee that only 1 thread is using a connection at any given point)
>
>
> Thanks for your help,
>
> --
> Attila
> Software Developer
> attee...@gmail.com
>



-- 
Attila
Software Developer
attee...@gmail.com

mysqlpp::Connection memory leak?

[Attila]

Hi Everyone,

I have an application that uses a custom made DBConnectionPool.
The architecture is basically as follows:

All of the components (DBConnectionPool and DBWorker) run in their own
strands (all work is queued, so no explicit locking is required), that
is...  all work is run via threadpool threads.

DBConnectionPool passes out connections.
DBWorker's accept work (in the form of adding DBWork to it's list to process
when a connection is received)
  --> These DBWorkers will request a connection from the pool, the pool then
queues a connection for usage back to the DBWorker (when a connection
becomes available)

That all being said, I am using the thread aware libraries of mysql and
mysqlpp.

Here are a couple of stack traces I get on application shutdown from a
memory leak detector (using VLD 1.0 on VS 9.0):

Connect related:

  Call Stack:
f:\dd\vctools\crt_bld\self_x86\crt\src\dbgmalloc.c (56): malloc

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\my_once.c
(61): my_once_alloc

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\charset.c
(62): init_state_maps

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\charset.c
(435): init_available_charsets

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\mysys\charset.c
(577): get_charset_by_csname

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\sql-common\client.c
(1780): mysql_init_character_set

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\sql-common\client.c
(2177): mysql_real_connect
c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\dbdriver.cpp (89):
mysqlpp::DBDriver::connect
c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\connection.cpp (98):
mysqlpp::Connection::connect
c:\p4\dev\aa1\libs\toolsdatabase\mysqlppconnection.cpp (52):
db::MySQLppConnection::MySQLppConnection
c:\p4\dev\aa1\rstsrc\libs\toolsdatabase\mysqlppconnectionfactory.cpp
(41): db::MySQLppConnectionFactory::CreateDBConnection
(...omitted)

I also get a store-related memory leak:

 Call Stack:
f:\dd\vctools\crt_bld\self_x86\crt\src\dbgmalloc.c (56): malloc
g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\dbug\dbug.c
(2022): DbugMalloc
g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\dbug\dbug.c
(345): code_state
g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\dbug\dbug.c
(967): _db_enter_

g:\mysql-5.1.30-winbuild\mysql-community-debug-5.1.30-build\sql-common\client.c
(2837): mysql_real_query
c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\dbdriver.h (199):
mysqlpp::DBDriver::execute
c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\query.cpp (481):
mysqlpp::Query::store
c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\lib\query.cpp (472):
mysqlpp::Query::store
c:\p4\dev\aa1\libs\extlibs\mysql++-3.0.8\include\query.h (467):
mysqlpp::Query::store
c:\p4\dev\aa1\libs\toolsdatabase\mysqlppconnection.cpp (212):
db::MySQLppConnection::SelectExec
(...omitted)


I know that I am cleaning up my wrapper objects correctly. MySQLppConnection
has an auto_ptr to mysqlpp::Connection and I know the destructors are being
called.

Versions I am using:

mysqlpp:  3.0.8
mysql:  5.1.30
Running mysql server instance: 5.1.41


Questions:

Is my combination of versions incorrect?
Should I be using the mysql-c libraries for the same version as the running
server instance?
If I am passing a mysqlpp::Connection object around to different objects (in
different threads) -- could it cause a memory leak or other problems? (I can
guarantee that only 1 thread is using a connection at any given point)


Thanks for your help,

-- 
Attila
Software Developer
attee...@gmail.com

Re: MySQL Replication Delete is not gettting replicated

[Carlos Proal]

I dont see anything unusual or missing on your config file and as the 
only thing missing are deletes, i think that might be a permission issue.


Can you check out the grants for your replication users and see if they 
have full permissions granted ?


mysql> show grants for x;

where is x is replication and replication2 respectively.

Carlos


On 1/18/2010 1:35 AM, Manasi Save wrote:

Hi Anand,

Please find below my configuration file of both the masters:

ON MASTER 1:

[mysqld]
datadir=/var/lib/mysql/
socket=/var/lib/mysql/mysql.sock
old_passwords=1

log-bin=/usr/local/mysql/bin.log
#binlog-do-db=  # input the database which should 
be replicated
binlog-ignore-db=mysql# input the database that should be 
ignored for replication

binlog-ignore-db=test
log-bin-index=/usr/local/mysql/log-bin.index
log_slave_updates

server-id=2

auto_increment_increment=2
auto_increment_offset=1

#information for becoming slave.
master-host = 192.168.1.1
master-user = replication
master-password = replication
master-port = 3306

[mysql.server]
user=mysql

[mysqld_safe]
err-log=/var/lib/mysql/mysql.log
pid-file=/var/lib/mysql/mysql.privatedns.com.pid

ON MASTER 2:

[mysqld]
datadir=/var/lib/mysql/
socket=/var/lib/mysql/mysql.sock
old_passwords=1

log-bin=/usr/local/mysql/bin.log
#binlog-do-db=  # input the database which should 
be replicated
binlog-ignore-db=mysql# input the database that should be 
ignored for replication

binlog-ignore-db=test
log-bin-index=/usr/local/mysql/log-bin.index
log_slave_updates

server-id=1

auto_increment_increment=2
auto_increment_offset=2

#information for becoming slave.
master-host = 192.168.1.2
master-user = replication2
master-password = replication2
master-port = 3306

[mysql.server]
user=mysql

[mysqld_safe]
err-log=/var/var/lib/mysql/mysql.log
pid-file=/var/lib/mysql/mysql.privatedns.com.pid

Please let me know if I need to add any parameter to enable this 
replication.


Thanks in advance.

--

Regards,

Manasi Save



Quoting Anand kumar :

can you give us the configuration(.cnf) file from both the masters ?
--Anand
On Sat, Jan 16, 2010 at 3:06 PM, Manasi Save
mailto:manasi.s...@artificialmachines.com>> wrote:

Hi All,


I have configured MySQL Master-Master Replication on my
servers. When I am inserting or updating any data in a regular
table the data is getting replicated.


But When I am doing delete on that same table. the data is
only getting deleted only on the server where I am doing
delete. but it is not getting replicated on its slave.


Even if I am doing truncate it is not getting replicated. Can
anyone provide any input on this?


Thanks in advance.


--

Regards,

Manasi Save

Re: Record old passwords ?

[Carlos Proal]

On 1/18/2010 6:52 PM, Colin Streicher wrote:

On January 18, 2010 01:34:15 pm Tompkins Neil wrote:
   

Hi

I'm in the process of designing a login system to a secure web page using
MySQL.  One of the features is we need to record and ensure that the user
password is different from any of the last four passwords he/she has used.
  I was thinking of create four fields called Password1, Password2,
  Password3 and Password4 to record the old passwords.

Is this a preferred method - or does anyone else have any recommendations ?

Thanks,
Neil

 

I'm not an awesome database designer, most of what I do is code related stuff,
I think what I would do for this is 1. hash the password( sha256/512 whatever)
and then 2. store the hash in a string with delimiters. In that way, you solve
2 problems.
You can store as many as you want to because you can just check hashes to make
sure it isn't the same, and second, you aren't storing passwords in plain-
text, which is a personal pet peeve.

   


Neil,
As others appointed, having another table with old passwords is a good 
"design" solution, and can allow you to have more than 4 passwords on 
your history. But in fact your solution is the best solution for 
performance and is called "denormalization", this solution gives good 
performance because in 1 read you get all the passwords but has the 
limitation of be "fixed" to only 4 passwords (which is not so bad 
because you can add new columns as needed, you will never have 20 
history passwords anyway, do you ?).
So, thats the trade, design vs performance, you should pick the best for 
you.


The solution proposed by Colin is another way to do it but, from the 
good design perspective is NOT a good solution, is what its called a 
"multivalued attribute" and all those should be avoided. But again, is 
up to you.


Carlos



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Record old passwords ?

[John Meyer]

On 1/18/2010 5:52 PM, Colin Streicher wrote:

On January 18, 2010 01:34:15 pm Tompkins Neil wrote:

Hi

I'm in the process of designing a login system to a secure web page using
MySQL.  One of the features is we need to record and ensure that the user
password is different from any of the last four passwords he/she has used.
  I was thinking of create four fields called Password1, Password2,
  Password3 and Password4 to record the old passwords.

Is this a preferred method - or does anyone else have any recommendations ?

Thanks,
Neil


I'm not an awesome database designer, most of what I do is code related stuff,
I think what I would do for this is 1. hash the password( sha256/512 whatever)
and then 2. store the hash in a string with delimiters. In that way, you solve
2 problems.
You can store as many as you want to because you can just check hashes to make
sure it isn't the same, and second, you aren't storing passwords in plain-
text, which is a personal pet peeve.




Almost always, when you start thinking of fields with numbers at the end 
of their names, you should move that off to another table.  Example:



PASSWORD_HISTORY
PW_ID
USER_ID  <--foreign key linking to the user table
PW_ENTRY
PW_ENTRYDATE


That way all you have to do is write this query:

SELECT * FROM PASSWORD_HISTORY WHERE USER_ID='entry' ORDER BY 
PW_ENTRYDATE DESC LIMIT 4;



Although, on an OT, forcing people to not use a password that they have 
recently used is a bad idea.  What they eventually do is go with 
something like "hometown01" "hometown02", etc.  Or worse, they start 
writing down their passwords which is a whole other security problem.






--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Record old passwords ?

[Colin Streicher]

On January 18, 2010 01:34:15 pm Tompkins Neil wrote:
> Hi
> 
> I'm in the process of designing a login system to a secure web page using
> MySQL.  One of the features is we need to record and ensure that the user
> password is different from any of the last four passwords he/she has used.
>  I was thinking of create four fields called Password1, Password2,
>  Password3 and Password4 to record the old passwords.
> 
> Is this a preferred method - or does anyone else have any recommendations ?
> 
> Thanks,
> Neil
> 
I'm not an awesome database designer, most of what I do is code related stuff, 
I think what I would do for this is 1. hash the password( sha256/512 whatever) 
and then 2. store the hash in a string with delimiters. In that way, you solve 
2 problems. 
You can store as many as you want to because you can just check hashes to make 
sure it isn't the same, and second, you aren't storing passwords in plain-
text, which is a personal pet peeve. 
 
-- 
In the stairway of life, you'd best take the elevator.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Record old passwords ?

[Carsten Pedersen]

Using multiple columns to hold essentially the same data is generally a 
bad idea: Business requirements may change over time, forcing you to 
change both the schema and your programming logic.


Better to use a table consisting of username/changedate/password. One 
year from now, when  your boss/customer decides to up the requirement to 
six passwords, it will be a simple app change.


/ Carsten

Tompkins Neil skrev:

Hi

I'm in the process of designing a login system to a secure web page using
MySQL.  One of the features is we need to record and ensure that the user
password is different from any of the last four passwords he/she has used.
 I was thinking of create four fields called Password1, Password2, Password3
and Password4 to record the old passwords.

Is this a preferred method - or does anyone else have any recommendations ?

Thanks,
Neil


!DSPAM:451,4b54a9e956471140923725!



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Regarding storing non-english chars in mysql

[fsb]

you can specify the character encoding (called CHARSET in mysql) and
collation on a per column, per table or per database level. e.g.

CREATE DATABASE foo CHARACTER SET utf8 COLLATE utf8_general_ci;

or

CREATE TABLE foo ( ... ) CHARACTER SET utf8 COLLATE utf8_general_ci;

or

CREATE TABLE foo (
bar varchar(128) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL);

mysql's default character encoding is latin1.

for mysql's collations, see: http://www.collation-charts.org/

i wouldn't use utf8 indiscriminately, only for columns that need it --
indexes need 3 bytes per character on utf8 columns. (utf16 would be better
in that regard!)

don't forget to set session system variables, e.g. using SET NAMES or with
your api.


On 1/18/10 2:44 PM, "Gavin Towey"  wrote:

> http://dev.mysql.com/doc/refman/5.0/en/charset.html
> 
> 
> -Original Message-
> From: Ningappa Koneri [mailto:ningappa.kon...@comviva.com]
> Sent: Sunday, January 17, 2010 11:32 PM
> To: mysql@lists.mysql.com
> Subject: Regarding storing non-english chars in mysql
> 
> Dear all,
> 
> I have a problem in migrating a GUI app(displays multi lingual data like
> Arabic) which currently uses oracle as backend db to mysql (5.1). Currenly in
> oracle I am using NVARCHAR datatype to store the Arabic chars. How do I
> incorporate the same functionality in mysql ? I have tried a sample
> servlet/jsp to insert the arabic chars into mysql by creating a table having
> two columns of NATIONAL VARCHAR type, but it's not displaying Arabic chars
> instead only questions marks are there.
> 
> One more thing in sample example is that before inserting I am converting to
> UTF-8.
> 
> Regards,
> Ningappa Koneri
> mLifestyle | www.comviva.com
> 
> 
> This e-mail and all material transmitted with it are for the use of the
> intended recipient(s) ONLY and contains confidential and/or privileged
> information. If you are not the intended recipient, please contact the sender
> by reply e-mail and destroy all copies and the original message. Any
> unauthorized review, use, disclosure, dissemination, forwarding, printing or
> copying of this email or any action taken pursuant to the contents of the
> present e-mail is strictly prohibited and is unlawful.
> The recipient acknowledges that Comviva Technologies Limited or its management
> or directors, are unable to exercise control or ensure the integrity over /of
> the contents of the information contained in e-mail. Any views expressed
> herein are those of the individual sender only and no binding nature of the
> contents shall be implied or assumed unless the sender does so expressly with
> due authority of Comviva Technologies Limited. E-mail and any contents
> transmitted with it are prone to viruses and related defects despite all
> efforts to avoid such by Comviva Technologies Limited.
> 
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql?unsub=gto...@ffn.com
> 
> 
> This message contains confidential information and is intended only for the
> individual named.  If you are not the named addressee, you are notified that
> reviewing, disseminating, disclosing, copying or distributing this e-mail is
> strictly prohibited.  Please notify the sender immediately by e-mail if you
> have received this e-mail by mistake and delete this e-mail from your system.
> E-mail transmission cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses. The sender therefore does not accept liability
> for any loss or damage caused by viruses or errors or omissions in the
> contents of this message, which arise as a result of e-mail transmission.
> [FriendFinder Networks, Inc., 220 Humbolt court, Sunnyvale, CA 94089, USA,
> FriendFinder.com
> 
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql?unsub=...@thefsb.org
> 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

RE: When using "FOR UPDATE" whole the table seems to lock instead of selected row

[Gavin Towey]

I think Baron was referring to a technique like this:

you sell a t-shirt, UPDATE table SET t=t-X WHERE t >= X, if you get rows 
affected, it's sold and ok. if not, the stock ran out before the operation. but 
it's safe. see 
http://dev.mysql.com/tech-resources/articles/storage-engine/part_3.html


-Original Message-
From: phark...@gmail.com [mailto:phark...@gmail.com] On Behalf Of Perrin Harkins
Sent: Friday, January 15, 2010 6:08 AM
To: Johan Machielse
Cc: Baron Schwartz; mysql@lists.mysql.com
Subject: Re: When using "FOR UPDATE" whole the table seems to lock instead of 
selected row

On Fri, Jan 15, 2010 at 2:54 AM, Johan Machielse
 wrote:
> The problem is that multiple users can read and update the same field
> simultaneously (worse case) which could lead to unpredictable problems.

There are other ways to do handle most cases.  For example:
UPDATE table SET value = value + 1 WHERE key = 7;

If you need to grab the value after the insert, you can get it from
last_insert_id:
UPDATE table SET value = last_insert_id(value + 1) WHERE key = 7;

However, if your situation is more complex than that, FOR UPDATE is
usually a good solution.

> What I really want is the following:
> When person A is reading and updating a field value, person B should not be
> able to do this simultaneously. Person B has to wait till the Person A has
> finished his work.

FOR UPDATE is the right solution for that.  Your only issue seems to
be that you feel too many rows are being locked.  That's an internal
implementation issue, but you may be able to change it by adjusting
which columns have indexes and keeping your statistics up to date.  Or
there  may not be enough cardinality on the column you're using in the
query to lock specific rows.  Using EXPLAIN on the SELECT query might
tell you more about what's happening.

- Perrin

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=gto...@ffn.com


This message contains confidential information and is intended only for the 
individual named.  If you are not the named addressee, you are notified that 
reviewing, disseminating, disclosing, copying or distributing this e-mail is 
strictly prohibited.  Please notify the sender immediately by e-mail if you 
have received this e-mail by mistake and delete this e-mail from your system. 
E-mail transmission cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. The sender therefore does not accept liability 
for any loss or damage caused by viruses or errors or omissions in the contents 
of this message, which arise as a result of e-mail transmission. [FriendFinder 
Networks, Inc., 220 Humbolt court, Sunnyvale, CA 94089, USA, FriendFinder.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

RE: Regarding storing non-english chars in mysql

[Gavin Towey]

http://dev.mysql.com/doc/refman/5.0/en/charset.html


-Original Message-
From: Ningappa Koneri [mailto:ningappa.kon...@comviva.com]
Sent: Sunday, January 17, 2010 11:32 PM
To: mysql@lists.mysql.com
Subject: Regarding storing non-english chars in mysql

Dear all,

I have a problem in migrating a GUI app(displays multi lingual data like 
Arabic) which currently uses oracle as backend db to mysql (5.1). Currenly in 
oracle I am using NVARCHAR datatype to store the Arabic chars. How do I 
incorporate the same functionality in mysql ? I have tried a sample servlet/jsp 
to insert the arabic chars into mysql by creating a table having two columns of 
NATIONAL VARCHAR type, but it's not displaying Arabic chars instead only 
questions marks are there.

One more thing in sample example is that before inserting I am converting to 
UTF-8.

Regards,
Ningappa Koneri
mLifestyle | www.comviva.com


This e-mail and all material transmitted with it are for the use of the 
intended recipient(s) ONLY and contains confidential and/or privileged 
information. If you are not the intended recipient, please contact the sender 
by reply e-mail and destroy all copies and the original message. Any 
unauthorized review, use, disclosure, dissemination, forwarding, printing or 
copying of this email or any action taken pursuant to the contents of the 
present e-mail is strictly prohibited and is unlawful.
The recipient acknowledges that Comviva Technologies Limited or its management 
or directors, are unable to exercise control or ensure the integrity over /of 
the contents of the information contained in e-mail. Any views expressed herein 
are those of the individual sender only and no binding nature of the contents 
shall be implied or assumed unless the sender does so expressly with due 
authority of Comviva Technologies Limited. E-mail and any contents transmitted 
with it are prone to viruses and related defects despite all efforts to avoid 
such by Comviva Technologies Limited.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=gto...@ffn.com


This message contains confidential information and is intended only for the 
individual named.  If you are not the named addressee, you are notified that 
reviewing, disseminating, disclosing, copying or distributing this e-mail is 
strictly prohibited.  Please notify the sender immediately by e-mail if you 
have received this e-mail by mistake and delete this e-mail from your system. 
E-mail transmission cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. The sender therefore does not accept liability 
for any loss or damage caused by viruses or errors or omissions in the contents 
of this message, which arise as a result of e-mail transmission. [FriendFinder 
Networks, Inc., 220 Humbolt court, Sunnyvale, CA 94089, USA, FriendFinder.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Re: Record old passwords ?

[SH]

I'm still pretty new on the list, so take it easy on me if I'm way off
base.  But I think you'd be better off with a table just for old
passwords.  I think you could get by with four columns: id(primary
key), user_id, old_pw, change_date.  It should make your validation
query and inserts much easier.  You could simply "select * from
oldpwtbl where user_id='theuser' order by change_date desc limit 4;"
(disregard my poor syntax) to see if they are repeating.

One other thing I think would be more secure is to store a hash of the
password, instead of the password itself.

Anyway, that's my input.

Scott

On Mon, Jan 18, 2010 at 12:34 PM, Tompkins Neil
 wrote:
> Hi
>
> I'm in the process of designing a login system to a secure web page using
> MySQL.  One of the features is we need to record and ensure that the user
> password is different from any of the last four passwords he/she has used.
>  I was thinking of create four fields called Password1, Password2, Password3
> and Password4 to record the old passwords.
>
> Is this a preferred method - or does anyone else have any recommendations ?
>
> Thanks,
> Neil
>

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

Record old passwords ?

[Tompkins Neil]

Hi

I'm in the process of designing a login system to a secure web page using
MySQL.  One of the features is we need to record and ensure that the user
password is different from any of the last four passwords he/she has used.
 I was thinking of create four fields called Password1, Password2, Password3
and Password4 to record the old passwords.

Is this a preferred method - or does anyone else have any recommendations ?

Thanks,
Neil

Re: 32bit ( php + mysql server ) on 64bit Windows 2003 Server performance

[Edward S.P. Leong]

Jerry Schwartz wrote:

> From: Edward S.P. Leong [mailto:edward...@ita.org.mo]
> Sent: Friday, January 15, 2010 8:03 AM
> To: Jerry Schwartz
> Cc: mysql@lists.mysql.com
> Subject: Re: 32bit ( php + mysql server ) on 64bit Windows 2003 Server
> performance
>
> Jerry Schwartz wrote:
>
>BTW, would you mind to tell me which newer version of php and mysql are
>
>you running now ?
>
>Due to I want to download a version of them and do the test under win2003...
>
>Then, I want to tell(reply) you the result(stable)!
>
>??? 
>
>[JS] PHP 5.2.10, Apache 2.2.14 (Win32), MySQL 5.1.36-community
>
>? 
>
> Dear Jerry,
>
> Did you means :
> php (32 Bit) + Apache (32 Bit) + MySQL (32 Bit) on Windows (64 Bit) OS ?
>
> [JS] Sorry I didn?�t specify:
>
> PHP (32 bit)
>
> Apache (32 bit)
>
> MySQL (64 bit)
>
Dear Jerry,

1, Would you mind to send me your php.ini for reference ?
2, how to config the php connect to remote MS-SQL 2000 Server ?
3, And do you know does it good for working with aspx and MS-SQL 2000
Server also ?
Due to the dot net framework 32Bit / 64Bit problem...

Thank for your help !

Edward.

Re: Performance Innodb my.cnf

[Suresh Kuna]

Hi Ortis,
How abt the hits or load i.e ( DML, DDL ) to the server.
My initial assessment after looking at you cnf file is
1) Calculate and place an appropriate value for innodb_buffer_pool_size
2) Reduse  the innodb_thread_concurrency to 4 or 8.

and how about the no. of tables in the database and the table type.



On Sun, Jan 17, 2010 at 3:03 AM, Junior Ortis  wrote:

> Hi guys, first thanks for all help, this list is amazing.
>
> Well i have a dedicated server on Fedora 11 x64, its have 12GB ram and
> a SCSI 15k rpm on datadir.
>
> I need a improve on my mysql conf to that my software run better, its
> my.cnf  HOW i Can improve this :D
>
> Thanks !!
>
> HERE:
>
> [client]
> #password   = [your_password]
> port= 3306
> socket  = /tmp/mysql.sock
>
> # *** Application-specific options follow here ***
>
> #
> # The MySQL server
> #
> [mysqld]
> # generic configuration options
> port= 3306
> socket  = /tmp/mysql.sock
> skip-locking
> skip-external-locking
> datadir = /disk3/mysql
> net_buffer_length   = 1024K
> join_buffer_size= 1M
> sort_buffer_size= 4M
> read_buffer_size= 4M
> read_rnd_buffer_size= 4M
> table_cache = 500
> max_allowed_packet  = 16M
>
> max_connections=30
> max_user_connections=200
>
> key_buffer  = 1000M
> key_buffer_size = 1000M
> #thread_cache   = 400
> thread_stack= 128K
> thread_cache_size   = 1024
> thread_concurrency  = 8
> #thread_stack   = 128K
>
> default-character-set   = utf8
> innodb_flush_method=O_DIRECT
> innodb_buffer_pool_size= 11000M
> innodb_additional_mem_pool_size=10M
> innodb_log_file_size= 256M
> innodb_log_buffer_size=4M
> innodb_flush_log_at_trx_commit=0
> innodb_thread_concurrency=32
> innodb_file_per_table
> innodb_table_locks=0
>
> query_alloc_block_size  = 16k
>
> query_cache_limit   = 512M
> query_cache_size= 512M
> query_cache_type= 1
>
> long_query_time = 3
> table_cache = 800
> #innodb_force_recovery = 3
> table_definition_cache = 800
> query_cache_min_res_unit = 5K
> delay-key-write=OFF
> innodb_read_io_threads = 16
> innodb_write_io_threads = 16
> innodb_support_xa = false
> innodb_io_capacity = 1
> innodb_max_dirty_pages_pct = 90
>
> concurrent_insert   = 2
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=sureshkumar...@gmail.com
>
>


-- 
Thanks
Suresh Kuna
MySQL DBA