Collate issue

Hello,

I have a file that contains some SQL statements including CREATE TABLE, =
INSERT, UPDATE and specially CREATE VIEW. This file is used to apply =
changes into the database.

All databases & tables use the 'DEFAULT CHARSET=3Dlatin1 =
COLLATE=3Dlatin1_General_CS', so when creating views, the fields that =
exists in the table I am querying will have the same collation. However, =
new fields created by the SELECT do not use the collation I want: =
'latin1_General_CS'.

The first line of this file is: SET NAMES latin1 COLLATE =
latin1_general_cs;

So, when running -> mysql -u myuser -p testdb < settings.sql

The views are created using the 'latin1_General_CS'.

However, when I try to do the same in the MySQL installed on our servers =
(5.0.51a-3ubuntu5.5 and 5.0.32-Debian_7etch1), the views do not get =
created as they were on my local computer. Some fields are created using =
'latin1_swedish_ci', some as 'latin1_bin', and others without any.

Is there any known issue with previous versions of the MySQL 5.0.x =
regarding this?

Is there a way I can do this so all applicable fields on my view uses =
the collation I want?

Thanks for any help!

Andre

--
Andre Matos
andrematos@mineirinho.org





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=3Dgcdmg-mysql-2@m.gmane.o rg

Patching MySQL CLI to log information

--MCBoundary=_111060216440802801
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

Has anyone ever patched the MySQL or libmysql to log to some logfiles
with information like the UNIX user, time, server connected to, port
etc?

I'm just trying to save myself a bit of C patching.

Cheers,

A

------------------------------------------------------------ ---------------=
------------------------------------------------------------ --
LOVEFiLM UK Limited is a company registered in England and Wales.=20
Registered Number: 06528297.=20
Registered Office: No.9, 6 Portal Way, London W3 6RU, United Kingdom.

This e-mail is confidential to the ordinary user of the e-mail address to w=
hich it was addressed. If you have received it in error,=20
please delete it from your system and notify the sender immediately.

This email message has been delivered safely and archived online by Mimecas=
t.
For more information please visit http://www.mimecast.co.uk=20
------------------------------------------------------------ ---------------=
------------------------------------------------------------ --
--MCBoundary=_111060216440802801--