RE: [LIKELY JUNK]_UNICODE and DEFAULT_CODE

Hi,

_UNICODE has to be set to YES to allow UNICODE-data in the database

The default-value of _UNICODE was not changed in 7.5-versions. It is NO.

To influence the problem with the output too long, some help of clients
(which kind of client do you use?) and/or a server-version 7.6 would be =
needed

  Elke
SAP Labs Berlin
=20
Sitz der Gesellschaft/Registered Office: Walldorf, Germany

Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai =
Agassi, L=E9o Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, =
Peter Zencke

Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: =
Hasso Plattner

Registergericht/Commercial Register Mannheim No HRB 350269

Diese E-Mail kann Betriebs- oder Gesch=E4ftsgeheimnisse oder sonstige =
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail =
irrt=FCmlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, =
eine Vervielf=E4ltigung oder Weitergabe der E-Mail ausdr=FCcklich =
untersagt.

Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. =
Vielen Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or =
otherwise confidential information. If you have received this e-mail in =
error, you are hereby notified that any review, copying, or distribution =
of it is strictly prohibited. Please inform us immediately and destroy =
the original transmittal. Thank you for your cooperation.=20

=20

> -----Original Message-----
> From: Gerd K=F6nig [mailto:[email protected]]=20
> Sent: Dienstag, 31. Juli 2007 09:30
> To: [email protected]
> Subject: [LIKELY JUNK]_UNICODE and DEFAULT_CODE
>=20
> Hi,
>=20
> how do the parameters "_UNICODE" and "DEFAULT_CODE" influence=20
> each other ?
> The problem is, that we want to have _UNICODE=3DNO (otherwise we get
> OUTPUT column too long error), and the default code for=20
> character data =3D
> UNICODE (or at least in some tables we want to have unicode character
> data to be stored (varchar(xyz) UNICODE) )
> But this is not possible because DBM-Gui offers doesn't accept UNICODE
> for default_code while _UNICODE is set to NO.
>=20
> Does this _UNICODE=3DNO disable unicode support in general for the =
whole
> database ?
> And why has the default setting of _UNICODE changed in recent versions
> from "NO" to "YES" ?
>=20
> currently we're running MaxDB 7.5.0.44 both linux and win2k3server
>=20
> thanks in advance..GERD..
>=20
> --=20
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe:   =20
> http://lists.mysql.com/[email protected]
>=20
>=20

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[email protected]