Lukasz Misztal wrote :
> Hi,
>
> i try execute (example) SQL statement:
>
> CREATE TABLE "TableT1"
> (
> "MT_ID" Fixed (10,0) NOT NULL DEFAULT SERIAL (1),
> "MT_Name" Varchar (200) UNICODE NOT NULL,
> "MT_Value" Fixed (15,5) NOT NULL DEFAULT 1.00000,
> PRIMARY KEY ("MT_ID"),
> CONSTRAINT "CS_Value" CHECK "MT_Value" <> 0
> )
> //
> ALTER TABLE "TableT1" MODIFY ("MT_Name" VARCHAR (60) UNICODE)
> //
> ALTER TABLE "TableT1" MODIFY ("MT_Name" VARCHAR (80) UNICODE)
> //
> drop table "TableT1"
>
> and I get error:
>
> Auto Commit: On, SQL Mode: Internal, Isolation Level: Serializable
> Syntax error or access violation;-3014 POS(2) Invalid end of
> SQL statement
>
> Question is:
> 1. why constraint prevents from second alter table?
> 2. why MT_Value (not "MT_Value") works fine?
>
> It is a bug?
>
> Best regards,
>
> Lukasz
>
> Tested on:
> MAXDB 7.6.00.34, WIN XP Prof,
> MAXDB 7.6.00.37, WIN XP Prof,
> SQL Studio 7.6.00.27 (123692)
>
>
Hi Lukasz,
unfortunatly this is a bug, which has to do with the special identifiers used.
The first alter table statement leaves a wrong entry in the catalog,
which causes the error in the second alter table statement.
Thank you for reporting the bug,
Best regards,
Thomas
Thomas Anhaus
MaxDB&liveCache
SAP AG
Rosenthaler Str. 30
10178 Berlin
mailto: [EMAIL PROTECTED]
www.sap.com
Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi,
Léo 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äftsgeheimnisse oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung
oder Weitergabe der E-Mail ausdrücklich 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.
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
