Hello,
I'm using MySQL 4.1.2 and it should be available utf8_polish_ci
collation. But, it seems that it is not.
# Query:
# SHOW COLLATION LIKE 'utf%'
#
'Collation''Charset','Id','Default','Compiled','Sortlen'
'utf8_general_ci','utf8','33','Yes','Yes','1'
'utf8_bin','utf8','83','','Yes','1'
The sa
Hello,
I've just installed 4.1.1 to see how UTF-8 is working. In my.ini I have
set default-character-set=utf8 - so all input/output data should be send
in utf-8 charset. System variables (after start) are set as they should:
character_set_serverutf8
character_set_systemut
In the documentation there is a note that 4.1.2 will be released soon. I
need some features which are available only in this version... Any
estimated date when it will be ? Sorry for asking about the same thing...
ML
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
Hello,
when do you plan to release 4.1.2 version ?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Can you tell us, when you plan to release 4.1.1 version ?
A few weeks ago, Heikki guess was: ...before Nov 15th, 2003.
And how it looks now ?
Best regards,
ML
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTE
> I need to have a table that supports FULLTEXT searches. This
> implies that this table should be a MyISAM table.
>
> However, I also require that this table act as a parent for
> child tables in order to support referential integrity. If I
> create the child tables as INNODB tables, will ref
Hello,
I have a strange problem, maybe some of you will be able to explain me
something. I use LEFT JOIN as a substitute for subselects. It's true
that many subselects can be rewriten using LEFT JOIN. I have made a
query which use LEFT JOIN statement and... when there are many LEFT
JOIN's (over 3)
As far I remember full-text doesn't work with utf-8. Anybody knows the
estimated time when it will be supported ?? I next few months 4.1
version will be ready to use (I hope so...) and I wish to use utf-8
charsets, but very important issue is full-text search.
I'm also curious with InnoDB support
re
table's columns ??
Marek Lewczuk
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
> the correct syntax is WITHOUT quotes and WITHOUT spaces.
>
> --ft_min_word_len=2
>
> or
>
> -O ft_min_word_len=2 <-- but -O is obsolete
>
> but not
>
> -O 'ft_min_word_len = 2'
But we want to set this variable in my.cnf, so the syntax shouldn't be
like this:
set-variable = ft_mi
>
> At 8:20 +0100 7/22/03, Marek Lewczuk wrote:
> >On our Linux server we get this error:
> >030722 08:09:55 mysqld started
> >/usr/local/mysql/bin/mysqld: ERROR: unknown variable
> 'ft_min_word_len =
> >2' 030722 08:09:55 mysqld ended [...]
> >
On our Linux server we get this error:
030722 08:09:55 mysqld started
/usr/local/mysql/bin/mysqld: ERROR: unknown variable 'ft_min_word_len =
2'
030722 08:09:55 mysqld ended [...]
It's strange becouse I can set this variable through my.ini on my
Windows. Anyone can help me solve this problem ?
I'm trying to build mysql from the development sources of mysql 4.1.,
retreived using bitkeeper under win2k using cygwin.
I have made "bk -r edit", and now I'm having a problem
running aclocal:
aclocal: configure.in: 450: macro `AM_PROG_AS' not found in library
When I make "automake --version" a
> >I agree with your opinion in 100%, but in my case I need DBMS with
> >features like subselectes/utf-8/stored procedures but the
> speed is also
> >very important issue.
>
> You might have to spend money!
>
>
You are saying that there is DBMS with all this features and it is as
fast as MySQL
>
> which PostgreSQL version have you testet? If you want compare
> MySQL and
> PostgreSQL, than you have to use InnoDB tables. Tests with
> MyISAM make no
> sense. Out J2EE Application is working woth PostgreSQL 7.3.3
> and MySQL
> 4.0.13 with InnoDB tables (we need transactions and
> refe
> If maximum speed is critical.
>
> It's easy to lose sight of the fact that speed is not the
> only criterion
> in choosing a DBMS. Features, stability, security, and so on can be
> just as important or more so. No single DBMS is going to win all the
> prizes; the trick is to find the one
Hello group,
For everyone who thinks about moving from MySQL to PostgreSQL I have a
realy bad news - It's not worth. Why, You may ask... A few days ago I
have installed and tested PostgreSQL, becouse I realy need UTF-8 support
and subselects. I thought that PostgreSQL will be as good as MySQL but
a
Hello,
4.1 version can use UTF-8 encoding, but as far I remember there is
something wrong with this feature. Can you tell us when 4.1.1 version
will be released and is it will be fixed.
Best regards,
Marek
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsub
Hello,
As you all know InnoDB doesn't support full text search. My application
is a huge news system with about 100 new news per day. All of my tables
are in InnoDB becouse of foreign keys. Today I find out that the main
feature of news system - searching - is not available. It's quite big
problem.
is no model_id field inside... So mysql should not add two same
records...
>
> In article <[EMAIL PROTECTED]>,
> "Marek Lewczuk" <[EMAIL PROTECTED]> writes:
>
> > Hello group,
> > My table look like this:
>
> > CREATE TABLE `m
mda_models (make_id, model_name, model_phase,
model_phase_no, model_type) VALUES (42, 'Test model', NULL, NULL, 1);
MySQL should send an error before second query, that there is the record
which is the same as the inserting one... But NO, you can add as
21 matches
Mail list logo
