Problem with enforcement of a 'UNIQUE' constraint

I'm working on an object-oriented front-end for Oracle as a thesis project and am observing curious behavior with enforcement of a 'UNIQUE' constraint on an attribute. Here is a short description of the behavior:

If I create a table "by hand" like so:
create table t1
(n number UNIQUE NOT NULL);

and attempt to insert records with duplicate values for 'n', Oracle complains about a constraint violation, as it should.

If, however, I have my program construct the identical table creation command and send to Oracle, the table is apparently created without the 'UNIQUE' constraint. I can insert records with duplicate values for 'n', and Oracle does *not* complain.

Can anyone suggest why I am observing this difference in behavior, and how I might persuade Oracle to enforce this constraint?

Thanks very much!
Carolyn Giberson
giber_at_bubba.cs.uga.edu Received on Sun Feb 26 1995 - 13:48:10 CET