From user:
For AquaFold: the request is for a way to centrally define the primary key for Execute Edit against a particular database view. Since Sybase allows sp_primarykey for views, I’d suggest respecting the primary key entry.
sp_primarkey definition: http://infocenter.sybase.com/archive/topic/com.sybase.help.ase_15.0.sprocs/html/sprocs/sprocs178.htm
@ivan - Today, when execute edit is invoked, we check to see if a table has a PK defined. If so, we automatically check that PK in Table Data Editor. For views, we don't perform any such check since views typically don't have PKs associated w/ them. The enhancements request is that for Sybase ASE, check to see if a PK is defined for this view. If so, then automatically set those fields as PKs when TDE is launched.
sp_primarykey does not create an enforced referential integrity constraints on a table. Our extraction is only pulling enforced constraints information. We can create a new extraction for these non enforced objects and if there is no actual primary key on the table, then extract this information and use this. This can be done for tables and views.
These information is stored in the syskeys system table.
This can be done for tables and views.
Lets do this
This can be done for tables and views.
Lets do this
New extraction method for non enforced primary key constraints added to extractconstraints. Execute edit will now attempt to extract any non enforced primary key constraints if no enforced primary key constraints exists. This is currently only affective for sybase ase.
New extraction method for non enforced primary key constraints added to extractconstraints. Execute edit will now attempt to extract any non enforced primary key constraints if no enforced primary key constraints exists. This is currently only affective for sybase ase.
SybaseASE: Note that needs to be understood. The non enforced primary key will only be extracted if the object does not have an enforced primary key OR a unique constraint/index object. This means if you create a view/table without a primary key but place a unique constraint on the view/table, then execute sp_primarykey <column> on the object, the non enforced primary key will not be used over the enforced unique keys. We can re-visit how this is done, but this process would have the least impact how users currently experiencing datastudio.
SybaseASE: Note that needs to be understood. The non enforced primary key will only be extracted if the object does not have an enforced primary key OR a unique constraint/index object. This means if you create a view/table without a primary key but place a unique constraint on the view/table, then execute sp_primarykey <column> on the object, the non enforced primary key will not be used over the enforced unique keys. We can re-visit how this is done, but this process would have the least impact how users currently experiencing datastudio.
Issue #13263 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v15.0.15-1, v16.0.4-4, v17.0.0-dev-20 |
No time estimate |
sp_primarykey does not create an enforced referential integrity constraints on a table. Our extraction is only pulling enforced constraints information. We can create a new extraction for these non enforced objects and if there is no actual primary key on the table, then extract this information and use this. This can be done for tables and views.
These information is stored in the syskeys system table.