RE: Hebrew

2005-03-12 Thread John Berman

Greg

I use MySQL Control centre to access my dbase and I have set

My character_set_xxx variables to Hebrew

I then looked at the values, show variables like '%char%'; and all was fine.

However if I then exit MySQL Control centre and then go back to it my
character_set_xxx variables are all back at their defaults ?

I'm assuming this is a permissions type problem?


Regards

John B

-Original Message-
From: Gleb Paharenko [mailto:[EMAIL PROTECTED] 
Sent: 08 March 2005 21:06
To: mysql@lists.mysql.com
Subject: Re: Hebrew

Hello.

In most encodings english letters remain unchanged, but to be sure
you may execute set NAMES latin1 before quering tables with English
data.




John Berman [EMAIL PROTECTED] wrote:
 Thanks will do this.
 
 In the same dBase there a lots of tables were the data is in English - I
 assume they will be ok ?
 
 John B
 
 -Original Message-
 From: Gleb Paharenko [mailto:[EMAIL PROTECTED] 
 Sent: 07 March 2005 21:12
 To: mysql@lists.mysql.com
 Subject: Re: Hebrew
 
 Hello.
 
 Put all your character_set_xxx variables to hebrew. See:
 
  http://dev.mysql.com/doc/mysql/en/charset-connection.html
 
  
 
 John Berman [EMAIL PROTECTED] wrote:
 How's this
 
 
 +--+---+
 | Variable_name| Value |
 +--+---+
 | character_set_client | latin1|
 | character_set_connection | latin1|
 | character_set_database   | hebrew|
 | character_set_results| latin1|
 | character_set_server | latin1|
 | character_set_system | utf8  |
 | character_sets_dir   | /usr/mysql4/share/mysql/charsets/ |
 +--+---+
 
 
 John B
 
 -Original Message-
 From: Gleb Paharenko [mailto:[EMAIL PROTECTED] 
 Sent: 07 March 2005 12:28
 To: mysql@lists.mysql.com
 Subject: Re: Hebrew
 
 Hello.
 
 Pointers were I went wrong would be appreciated
 
 What's the default character set for your server? Please, send
 us an output of the following statement:
 
  show variables like '%char%';
 
 Please, use mysql command line client.
 
 
 
 John Berman [EMAIL PROTECTED] wrote:
 Using 4.1
 
 Though I had it cracked ?
 
 I created a new table and set the Charset to Hebrew and the field =
 =A0Collation
 to hebrew_general_ci=A0
 
 I then uploaded data to the database using MS Acess (with an ODBC
 connection)
 
 In MSAccess on my PC the Hebrew comes through fine.
 
 However when I open the newly created table using MSAccess or phpMyAdmin
 the Hebrew is represented with question marks.
 
 Pointers were I went wrong would be appreciated
 
 Regards
 
 John Berman
 
 --=20
 No virus found in this outgoing message.
 Checked by AVG Anti-Virus.
 Version: 7.0.308 / Virus Database: 266.6.2 - Release Date: 04/03/2005
 =20
 
 
 
 
 
 


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.0 - Release Date: 08/03/2005
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.2 - Release Date: 11/03/2005
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Tables and Unicode Characters

2005-03-12 Thread Segismundo
Hi all!
I've a problem with insert unicode characters on my database. I use
Mysql 4.1.10 on Win and Linux-Debian and I share the same database. My
server, client and database are on utf8 character, but my keyboard is on
Spanish.
I need introduce IPA characters on my table of a database whit or not
combine characters and I don't Know how to introduce them. For example:
 = U0100 or  = U0254 + U0354.
I use on Linux Rekall and I can select the font of any field, and with
OpenOffice write the 'word', copy and past. I Know that is not a solution.
How can I do it to see correctly?
Thanks
Segismundo

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Tables and Unicode Characters

2005-03-12 Thread Segis
Hi all!
I've a problem with insert unicode characters on my database. I use 
Mysql 4.1.10 on Win and Linux-Debian and I share the same database. My 
server, client and database are on utf8 character, but my keyboard is on 
Spanish.
I need introduce IPA characters on my table of a database whit or not 
combine characters and I don't Know how to introduce them. For example: 
 = U0100 or  = U0254 + U0354.
I use on Linux Rekall and I can select the font of any field, and with 
OpenOffice write the 'word', copy and past. I Know that is the solution. 
How can I do it to see correctly?
Thanks
Segismundo

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: insert - select from two different applications race condition?

2005-03-12 Thread Rhino

- Original Message - 
From: Aragorn [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Saturday, March 12, 2005 1:47 AM
Subject: insert - select from two different applications race condition?


 I have a simple problem...

 I'm using mysql 4.1.9/innodb table and two small python applications A and
B

 first application A is executed, and do a simple INSERT into a table
 then application B is executed:
 - B does a SELECT in the same table, that should return the entry
 created by application A
 (and based on the result, an UPDATE (to the entry application A has
 created) or an INSERT if it can't find it... but in this scenario it
 should find it since B is always executed just after A is)

 I can be sure that application A is executed before application B is
 started, even though B can be started just after A is done.

 The problem is that every once in a while, the SELECT doesn't return
 anything... even though I can check that application A created the
 entry...

 Everything looks as if the INSERT from application A hasn't completed
 when the SELECT in the application B is performed... Even though
 application A terminated before application B started!

 Any clue about what's going on?

 How can I prevent that?

Are you sure that Application A committed its INSERT before B attempted to
read the row?

Remember, the new row isn't accessible to Application B until A has done the
INSERT *AND* committed the INSERT (and released any locks it holds on the
table into which the row was inserted). You should be checking the return
code from the INSERT and the commit to ensure that both worked; if you
aren't doing that, either step could fail silently and leave you thinking
that the INSERT was successful or that it was successfully committed when it
wasn't. That would explain why Application B doesn't see the row.

The likelihood of this scenario can be minimized if you have turned
'autocommit' on; then, each statement is committed immediately upon
successful completion but, even then, the INSERT has to be successful before
the automatic commit has the desired effect. Again, you need to verify that
the INSERT was successful each time you do one.

Please note that I am NOT saying that you should always use autocommit!
There are many good reasons not to use autocommit, particularly when you
have some sort of multi-part transaction where all parts have to either
succeed or fail together. The classic example of this is a bank transfer
where you move money from one account to another; you definitely don't want
to commit until both the debit and the credit are complete.

--

The other thing you might want to consider is Application B. Is it possibly
encountering a lock that prevents it reading the row created by Application
A? If it tries to read the row before A has released the lock, which could
potentially happen if Application A hasn't committed (or, in some cases
ENDED), it might be encountering a lock preventing reading. Now, if you are
testing for that lock within your code and reacting appropriately, you
should be fine but if you simply return an empty result set without checking
for a lock, you might fool yourself into thinking the row is not there when
it is present but inaccessible.

Let me stress that this second scenario, the one where Application B
encounters a lock, may not be possible in MySQL. I don't know anything about
how locking works in MySQL. However, the situation I describe *is* possible
in DB2, which I've used for many years. Since MySQL behaves like DB2 in many
respects, it seems possible that this scenario could happen in MySQL as
well. But I could be dead wrong so please don't scream at me if I am.

Rhino



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.2 - Release Date: 11/03/2005


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



INSERT ON DUPLICATE KEY UPDATE

2005-03-12 Thread Aleksandr Guidrevitch
Hi all !
I'm having problem with INSERT ... ON DUPLICATE KEY UPDATE on mysql 4.1.10
--8--8--8--8--8--8--8--8--8
INSERT INTO lot_end (id, owner_id, category_id, title, current_price, 
buy_price, end_time, price, bid_count, currency_name)
SELECT lot.id, lot.owner_id, lot.category_id, lot.title, 
lot.current_price, lot.buy_price, lot.end_time, IF(lot.type_id = 2, 
lot.buy_price * exchange_rate.exchange_rate, lot.current_price * 
exchange_rate.exchange_rate) as priceA , COUNT(bid.id) as bid_countA, 
currency.name
FROM lot
   INNER JOIN bid
   ON bid.lot_id = lot.id
   INNER JOIN currency
   ON currency.id = lot.currency_id
   INNER JOIN exchange_rate
  ON exchange_rate.currency_id = lot.currency_id
WHERE lot.id = 1
GROUP BY lot.id
ON  DUPLICATE KEY
UPDATE lot_end.price = VALUES(priceA), lot_end.bid_count = 
VALUES(bid_countA);

--8--8--8--8--8--8--8--8--8
it reports ERROR 1054 (42S22): Unknown column 'priceA' in 'field list'
Also, I've tried
--8--8--8--8--8--8--8--8--8
...
on duplicate key update lot_end.price = IF(lot.type_id = 2, 
lot.buy_price * exchange_rate.exchange_rate,lot.current_price * 
exchange_rate.exchange_rate), lot_end.bid_count = COUNT(bid.id);

--8--8--8--8--8--8--8--8--8
and it reports ERROR  (HY000): Invalid use of group function
Could anyone tell me how to use ON DUPLICATE KEY UPDATE with GROUP BY 
functions ?

Sincerely,
Aleksandr Guidrevitch
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Limit of a sql script

2005-03-12 Thread Mauricio Pellegrini
Hi , 
I'm using mysql 4.1.4 gamma with InnoDB suse 8.2 reiser fs.

I'am doing backups using mysqldump which creates a sql script with the
structure for all tables plus the correspondig commands to create them
and also the data to be inserted in each one of them.

Latter when I have to restore one of these backups I create the
corresponding database an run the following from the shell

mysql db_name  db_name.sql

This seems to work just fine so far, but I'am concerned about the size
of this script ( db_name.sql has 450mb ).

My question is: there could be a size problem when mysql handles the
content of this script due to its size.

In other words is there a limit on the size of a script that mysql can
hable from the command line ?

I hope I've made myself clear

Best regards
Mauricio



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: INSERT ON DUPLICATE KEY UPDATE

2005-03-12 Thread Jocelyn Fournier
Hi,
It could perhaps be related to bug #8147.
http://bugs.mysql.com/bug.php?id=8147
Regards,
  Jocelyn
Aleksandr Guidrevitch a écrit :
Hi all !
I'm having problem with INSERT ... ON DUPLICATE KEY UPDATE on mysql 4.1.10
--8--8--8--8--8--8--8--8--8
INSERT INTO lot_end (id, owner_id, category_id, title, current_price, 
buy_price, end_time, price, bid_count, currency_name)
SELECT lot.id, lot.owner_id, lot.category_id, lot.title, 
lot.current_price, lot.buy_price, lot.end_time, IF(lot.type_id = 2, 
lot.buy_price * exchange_rate.exchange_rate, lot.current_price * 
exchange_rate.exchange_rate) as priceA , COUNT(bid.id) as bid_countA, 
currency.name
FROM lot
   INNER JOIN bid
   ON bid.lot_id = lot.id
   INNER JOIN currency
   ON currency.id = lot.currency_id
   INNER JOIN exchange_rate
  ON exchange_rate.currency_id = lot.currency_id
WHERE lot.id = 1
GROUP BY lot.id
ON  DUPLICATE KEY
UPDATE lot_end.price = VALUES(priceA), lot_end.bid_count = 
VALUES(bid_countA);

--8--8--8--8--8--8--8--8--8
it reports ERROR 1054 (42S22): Unknown column 'priceA' in 'field list'
Also, I've tried
--8--8--8--8--8--8--8--8--8
...
on duplicate key update lot_end.price = IF(lot.type_id = 2, 
lot.buy_price * exchange_rate.exchange_rate,lot.current_price * 
exchange_rate.exchange_rate), lot_end.bid_count = COUNT(bid.id);

--8--8--8--8--8--8--8--8--8
and it reports ERROR  (HY000): Invalid use of group function
Could anyone tell me how to use ON DUPLICATE KEY UPDATE with GROUP BY 
functions ?

Sincerely,
Aleksandr Guidrevitch

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Limit of a sql script

2005-03-12 Thread Jocelyn Fournier
Hi,
The only limit I'm aware of is the size of a query itself, which can not 
be bigger than the max_allowed_packet size.

Regards,
  Jocelyn
Mauricio Pellegrini a écrit :
Hi , 
I'm using mysql 4.1.4 gamma with InnoDB suse 8.2 reiser fs.

I'am doing backups using mysqldump which creates a sql script with the
structure for all tables plus the correspondig commands to create them
and also the data to be inserted in each one of them.
Latter when I have to restore one of these backups I create the
corresponding database an run the following from the shell
mysql db_name  db_name.sql
This seems to work just fine so far, but I'am concerned about the size
of this script ( db_name.sql has 450mb ).
My question is: there could be a size problem when mysql handles the
content of this script due to its size.
In other words is there a limit on the size of a script that mysql can
hable from the command line ?
I hope I've made myself clear
Best regards
Mauricio

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Problem: Too many connections

2005-03-12 Thread Steve Buehler
At 01:25 AM 3/12/2005, sapna murari todwal wrote:
Hi,
I have a live site using mysql. It is heavily used with over thousand 
users per minute, with 3 select / update   queries per user per minute 
accounting to over 3000 queries per minute.
The problem is that many times connection to this mysql server fails with 
the error Too many connection also sometimes the server becomes down 
bcoz of overload. The server has around 4GB of RAM with mysql version of 4.0.23
So my question is , is the problem related with just tuning of 
configuration parameters or can the problem be solved by any means too. 
Any kind of help is deeply appreciated.
Is it a single or dual processor?  Processor Speed?  Operating 
system?  Type of database.INNODB, MyISAM?  I don't have that many 
connections on any of my machines.  Since you are saying that your server 
is being overloaded and bogged down you might think about having a fast 
backend mysql cluster ( http://www.mysql.com/cluster ) instead of it on the 
same machine as your web server.  Possibly even a cluster for the web 
servers too, but you might not need that.  I am more curious about your 
processor(s).
We are creating a program that because of the high hits that we 
are expecting (actually more about processing then the number of hits 
through the web server itself), will have to have 3 clusters of servers to 
run it.  One cluster will be for the backend MySQL servers using MySQL's 
new (or relatively new) clustering.  I have never used it yet, but I think 
it would need at least 3 or 4 servers just to run it at its minimum for 
what we are going to be doing.  The second cluster will be for the web 
frontend.  We actually might be able to get away with just one frontend web 
server instead of the cluster though.  The third cluster will be for the 
special program that takes a minimum of 30 minutes (on a small test) to run 
for each client.  Some tests on live data have taken more than 5 hours to 
do all of the computations on a dual XEON with 2 gigs of mem.  You are 
getting more hits than we expect in any minute to your web server, but we 
will probably have more hits to the DB than you..maybe. :)  Or at least 
hits that take longer to get all of the data they need.

Steve
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


RE: Problem: Too many connections

2005-03-12 Thread Kostas Pyliouras
Back to the original problem ;)

Please post your my.cnf.

-Original Message-
From: Steve Buehler [mailto:[EMAIL PROTECTED] 
Sent: Samstag, 12. März 2005 16:02
To: mysql@lists.mysql.com
Subject: Re: Problem: Too many connections

At 01:25 AM 3/12/2005, sapna murari todwal wrote:

Hi,
I have a live site using mysql. It is heavily used with over thousand 
users per minute, with 3 select / update   queries per user per minute 
accounting to over 3000 queries per minute.
The problem is that many times connection to this mysql server fails with 
the error Too many connection also sometimes the server becomes down 
bcoz of overload. The server has around 4GB of RAM with mysql version of 4.0.23
So my question is , is the problem related with just tuning of 
configuration parameters or can the problem be solved by any means too. 
Any kind of help is deeply appreciated.

 Is it a single or dual processor?  Processor Speed?  Operating 
system?  Type of database.INNODB, MyISAM?  I don't have that many 
connections on any of my machines.  Since you are saying that your server 
is being overloaded and bogged down you might think about having a fast 
backend mysql cluster ( http://www.mysql.com/cluster ) instead of it on the 
same machine as your web server.  Possibly even a cluster for the web 
servers too, but you might not need that.  I am more curious about your 
processor(s).
 We are creating a program that because of the high hits that we 
are expecting (actually more about processing then the number of hits 
through the web server itself), will have to have 3 clusters of servers to 
run it.  One cluster will be for the backend MySQL servers using MySQL's 
new (or relatively new) clustering.  I have never used it yet, but I think 
it would need at least 3 or 4 servers just to run it at its minimum for 
what we are going to be doing.  The second cluster will be for the web 
frontend.  We actually might be able to get away with just one frontend web 
server instead of the cluster though.  The third cluster will be for the 
special program that takes a minimum of 30 minutes (on a small test) to run 
for each client.  Some tests on live data have taken more than 5 hours to 
do all of the computations on a dual XEON with 2 gigs of mem.  You are 
getting more hits than we expect in any minute to your web server, but we 
will probably have more hits to the DB than you..maybe. :)  Or at least 
hits that take longer to get all of the data they need.

Steve


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



MySQL/InnoDB-4.0.24 is released

2005-03-12 Thread Heikki Tuuri
Hi!
InnoDB is the MySQL table type that supports FOREIGN KEY constraints, 
transactions, row-level locking that is never escalated, multiversioned 
concurrency control, asynchronous unbuffered disk I/O on Windows, and a 
non-free online hot backup tool. InnoDB is an 'ACID'-compliant table type.

InnoDB is included in all MySQL downloads from http://www.mysql.com, and in 
the commercial MySQL Pro license.

Release 4.0.24 is a bugfix release of the old stable MySQL-4.0 branch.
Please observe this bug fix in upcoming 4.0.25:
* Fixed a bug: MySQL-4.0.23 and 4.0.24 could complain that an InnoDB table 
created with MySQL-3.23.49 or earlier was in the new compact InnoDB table 
format of 5.0.3 or later, and InnoDB would refuse to use that table. (The 
same bug exists in 4.1.8 - 4.1.10.) There is nothing wrong with the table, 
it is mysqld that is in error. Workaround: wait that 4.0.25 or 4.1.11 is 
released before doing an upgrade, or dump the table and recreate it with any 
MySQL version = 3.23.50 before upgrading to 4.0.23 or 4.0.24.

Full changelog for 4.0.24:
Functionality changed or added:
* Added configuration option and settable global variable 
innodb_autoextend_increment for setting the size in megabytes by which 
InnoDB tablespaces are extended when they become full. The default value is 
8, corresponding to the fixed increment of 8 MB in previous versions of 
MySQL.

* Do not acquire an internal InnoDB table lock in LOCK TABLES if 
AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB. 
InnoDB table locks in that case caused deadlocks very easily.

Bugs fixed:
* Work around a problem in AIX 5.1 patched with ML7 security patch: InnoDB 
would refuse to open its ibdata files, complaining about an operating system 
error 0.

* Fixed a memory corruption bug if one created a table with a primary key 
that contained at least two column prefixes. An example: CREATE TABLE t(a 
char(100), b tinyblob, PRIMARY KEY(a(5), b(10))).

* Use native tmpfile() function on Netware. All InnoDB temporary files are 
created under sys:\tmp. Previously, InnoDB temporary files were never 
deleted on Netware.

* Honor the --tmpdir startup option when creating temporary files. 
Previously, InnoDB temporary files were always created in the temporary 
directory of the operating system. On Netware, InnoDB will continue to 
ignore --tmpdir. (Bug #5822)

* Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs 
INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or 
DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this 
also fixes bug #7879 for InnoDB type tables. (Bug #7879)

* Fixed a bug: 32-bit mysqld binaries built on HP-UX-11 did not work with 
InnoDB files greater than 2 GB in size. (Bug #6189)

* Fixed a bug: InnoDB failed to drop a table in the background drop queue if 
the table was referenced by a foreign key constraint.

* Fixed a bug: if we dropped a table where an INSERT was waiting for a lock 
to check a FOREIGN KEY constraint, then an assertion would fail in 
lock_reset_all_on_table(), since that operation assumes no waiting locks on 
the table or its records.

Best regards,
Heikki Tuuri
Innobase Oy
http://www.innodb.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


show databases;

2005-03-12 Thread l'eau

I am on linux Fedora 2 with mysqld running as a daemon and the service mysql 
running (/etc/rc.d/init.d/).

I have two shell sessions (mysql client) running one with root and the other 
with a user.
I did (as root) : grant all privileges on mydb to [EMAIL PROTECTED];
in the root session the show databases; return 3 databases (test, mysql, mydb)
in the user session the show databases; return 1 database (test)


what is going on?

thanks
laurie

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Mysqldump alternative due to bug

2005-03-12 Thread Scott Klarenbach
I'm using Mysql 5.0.2 w/ Windows 2003 server, and there is a bug with
the mysqldump utility.  The bug is actually with the Describe table
statement, or Show fields from table statement...

It's been documented on mysql.com, so I'm wondering if there is a
simple alternative to mysqldump that I can use to backup the database,
until this bug is resolved in a future release?

Thanks,
Scott

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Problems with a full backup

2005-03-12 Thread Javier Ballesteros Correa
Hi! I'm learning mysql and I have a problem when i
make a full backup with mysqldump.
I have a lot of table rows written in spanish. In
the backup file (.sql) I have problems with certain
spanish characters like:
á -- Ãi
é -- é
í -- Ã-
ú -- ú
and so many others like that. 
However, when I make an incremental backup with the
*.bin-* files I don't have this problem.
I use MySQL 4.1.X with the default character
set(latin1) and the default collation
(latin1_swedish_ci). I´ve tried with the
latin1_spanish_ci and with another character set (utf8
with the utf8_spanish_ci collation). But the problem
doesn´t disappear.
Can anybody help me? Thank you very much. 



__ 
Renovamos el Correo Yahoo!: ¡250 MB GRATIS! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]