Query cache and queries with non-english characters
Just to be sure that this question is not supressed here :) Recently I've come around that mysql (4.1.0 at least) treats different queries containing non-english characters (in my case characters from cp1251 charset) as the same query and therefore returns wrong results. For example the following queries are regarded as identical while they are not: SELECT FROM table WHERE name LIKE 'при%' SELECT FROM table WHERE name LIKE 'про%' Is this a bug or expected behaviour? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Query cache and queries with non-english characters
Recently I've come around that mysql (4.1.0 at least) treats different queries containing non-english characters (in my case characters from cp1251 charset) as the same query and therefore returns wrong results. For example the following queries are regarded as identical while they are not: SELECT FROM table WHERE name LIKE 'при%' SELECT FROM table WHERE name LIKE 'про%' Is this a bug or expected behaviour? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions
> On Mon, Sep 29, 2003 at 09:33:29PM +0400, G B U wrote:
> >
> > Hmm... am I missing something?! IIRC there is nothing manual about Innodb
> > not supporting spatial extensions. And on windows it seems that all is working
> > fine. This is from my Win2000 box with the same Mysql version:
> >
> > mysql> create table t (p polygon not null, spatial index(p)) type=innodb;
> > Query OK, 0 rows affected (0.00) sec
> >
> > mysql> insert into t (p) values (geomfromtext('polygon((1 1, 2 2, 1 2, 1 1))'));
> > Query OK, 1 row affected (0.02) sec
> >
> > mysql> select astext(p) from t;
> > ++
> > | astext(p) |
> > ++
> > | POLYGON((1 1,2 2,1 2,1 1)) |
> > ++
> > 1 row in set (0.00 sec)
>
> Is it *really* an InnoDB table?
Yes it is really InnoDB table and I'm really confused now.
mysql> show table status like 't';
+--+++--++-+
-+--+---++-+-+--
--+---++--+
| Name | Type | Row_format | Rows | Avg_row_length | Data_length | Max_data_le
ngth | Index_length | Data_free | Auto_increment | Create_time | Update_time | C
heck_time | Charset | Create_options | Comment |
+--+++--++-+
-+--+---++-+-+--
--+---++--+
| t| InnoDB | Dynamic|1 | 16384 | 16384 |
NULL |16384 | 0 | NULL | NULL| NULL| N
ULL | latin1_swedish_ci || InnoDB free: 4096 kB |
+--+++--++-+
-+--+---++-+-+--
--+---++--+
1 row in set (0.01 sec)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions
> At 19:16 +0300 9/29/03, Victoria Reznichenko wrote:
> >"G B U" <[EMAIL PROTECTED]> wrote:
> >>
> >> It seems to me that combination from the subject just doesn't work.
> >> Every time I try to incorporate spatial column into Innodb table
> >> Mysql dies. The simplest case, easy to repeat is bellow.
> >> When I'm trying to create table with just one spatial column I'm
> >> getting following error:
> >>
> >> mysql> create table t (p polygon not null, spatial index(p)) type=innodb;
> >> ERROR 2013: Lost connection to MySQL server during query
> >>
> >> In error log mysql writes:
> >>
> >> assertion "0" failed: file "ha_innodb.cc", line 1547
> >> 030929 16:52:24 mysqld restarted
> >>
> >> I have two identical systems and both demonstrate behaviour
> >> described above.
> >>
> >> About systems config.
> >> Mysql: Version: '4.1.0-alpha'
> >> OS: FreeBSD 4.8-RELEASE
> >>
> >> So could someone test this and confirm or disconfirm above-mentioned
> >> abnormal behaviour.
> >>
> >
> >Currently you can use spatial columns only in the MyISAM tables.
>
>
> Also, the crash described above is fixed in MySQL 4.1.1. GIS features
> still are available only in MyISAM (as Victoria notes), but attempting
> to use them with InnoDB won't cause loss of connection or server restart.
Hmm... am I missing something?! IIRC there is nothing manual about Innodb
not supporting spatial extensions. And on windows it seems that all is working
fine. This is from my Win2000 box with the same Mysql version:
mysql> create table t (p polygon not null, spatial index(p)) type=innodb;
Query OK, 0 rows affected (0.00) sec
mysql> insert into t (p) values (geomfromtext('polygon((1 1, 2 2, 1 2, 1 1))'));
Query OK, 1 row affected (0.02) sec
mysql> select astext(p) from t;
++
| astext(p) |
++
| POLYGON((1 1,2 2,1 2,1 1)) |
++
1 row in set (0.00 sec)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions
Hi It seems to me that combination from the subject just doesn't work. Every time I try to incorporate spatial column into Innodb table Mysql dies. The simplest case, easy to repeat is bellow. When I'm trying to create table with just one spatial column I'm getting following error: mysql> create table t (p polygon not null, spatial index(p)) type=innodb; ERROR 2013: Lost connection to MySQL server during query In error log mysql writes: assertion "0" failed: file "ha_innodb.cc", line 1547 030929 16:52:24 mysqld restarted I have two identical systems and both demonstrate behaviour described above. About systems config. Mysql: Version: '4.1.0-alpha' OS: FreeBSD 4.8-RELEASE So could someone test this and confirm or disconfirm above-mentioned abnormal behaviour. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
