I am using ASE 15.7 and Visual Studio to import Sybase table
definitions into an Entity Fraemwork model (.edmx).

If I create the primary key with:

alter table tablename add primatry key (colname)

it works fine. But if I declare:

alter table tablename add constraint PK_name primary key
(colname)

Entity Framework complains about (colname) already existing
in the metadata collection and refuses to import the table.

I like to name the primary key constraint for several
reasons. One of those being when I go to drop the constraint
I don't have to look up the lengthy name assigned by Sybase.

Is there any way to name a primary key constraint which is
acceptable to Entity Framework? If not, is the Sybase Visual
Studio team aware of this as an issue?