I haven't used the jdbc.xml for a long time in favour of the external
datasource so I missed the new comment.
I gave it a try and it semms to work.
New idea. We create two mysql files in the database dir. One for utf8
and one for latin1. The utf8 version could be the default to match with
the mmbaseroot.xml encoding. The latin1 version could be used to switch
to the old behavior
Nico
Kees Jongenburger wrote:
On 6/28/06, *Nico Klasens* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
LS,
In several projects I have come across the same issue. I want to fix
this in the mmbase code Searches on fields with case-insensitive
queries fail, because rhe column in the database is of type blob. The
lower function does not work on blobs. I know that there are some
issues with mysql and enoding which mmbase works around by adding
bytes
to the database in iso8859-1 format. I don't want to change this.
Hi
actualy I performed some extensive test with mmbase and mysql with
mysql configured to use utf-8
and setting the database character encoding to utf-8 (see jdbc.xml
from mmbase_head)
The result wat that the database really contained what was expected
and that searching also worked.
This will create colums with type text to mysql which makes it
possible
to use the lower function. I have tested this change and didn't find
side-effect. Euro signs and other chanacters still work.
If I remeber correctly mysql only really searches the first 256
bytes/chars of the stream. just to you know.
Anybody objections for this change?
No, it will just help to do mysql full-text search on the fields.
------------------------------------------------------------------------
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
