Re: Oracle DBA Studio, almost useful

[Quoted] "Jarmo" <jarmo_at_jarmo.com> wrote in message news:3fbede7a$0$9390$ed9e5944_at_reading.news.pipex.net...
> I'm using Oracle DBA Studio to create my first table. It has a
> useful-looking table wizard into which I've entered the details of my new
> table. The wizard then proceeds to generate the (alleged) SQL equivalent
of
> my request. Problem is that when I click 'Finish' it rejects the
> auto-generated SQL claiming ORA-01741: illegal zero-length identifier.
>
> The auto-generated SQL looks like this:
>
> CREATE TABLE "SYSTEM"."EMPLOYEE"("EMPLOYEEID" NUMBER(4) NOT NULL,
> "NAME" VARCHAR2(128) NOT NULL,
> CONSTRAINT "" PRIMARY KEY("EMPLOYEEID"), UNIQUE("EMPLOYEEID"))
>
> I suspect that it's complaining about the CONSTRAINT "" which it inserted
> when I requested that EMPLOYEEID had to be unique. Disregarding the fact
> that the tool is bugged in allowing me to specify an illegal combination
of
> options, why must I provide a 'constraint'? And what would it be? Why
> isn't it sufficient to simply state that the column must contain unique
> values?

[Quoted] Because you need to create a unique constraint to enforce uniqueness.

> And, as an aside, can anyone tell me why Oracle persists in using arcane
> terminology such as NVARCHAR2 (rather than String) and why it doesn't
> support a boolean data type? Is it a deliberate attempt to deter the
casual
> user?

Well at least it has that in common with sqlserver then, which also doesn't [Quoted] support string datatypes. Perhaps that has someting to do with standard compliance.

-- 
Niall Litchfield
Oracle DBA
Audit Commission UK