SQL Power Software Forum

This message was edited 2 times. Last update was at 2010-03-09 22:38:29

Hi all.

Just started using SQLPA. After creating a new table and specifying the name of the primary key, I find that it isn't shown in the diagram. Why? I looked for a preference for this behavior, and didn't find one.

I did eventually find the "project settings" dialog, but the default is "show all columns." So no answers there...

I'm using version 0.9.16.

Thanks!

Hi, can you explain it in more detail and maybe add a screenshot?

You create a new table with a primary key and the primary key column doesn't show up?

Are you using Mac OS?

Thanks,
Benjamin

Benjamin wrote:You create a new table with a primary key and the primary key column doesn't show up?

Right.

Benjamin wrote:Are you using Mac OS?

Yep. 10.6.2.

Here's the screen shot:

Thanks for any insight.

Hi,

I only have a windows machine but I couldn't reproduce the problem.

Have you tried creating a normal column and just drag and drop it to the top area of the table where the primary key columns are? Will the column disappear?

Thanks,
Benjamin

Thanks for your reply, Benjamin.

No, moving the non-key column to the top doesn't make it disappear. It simply moves above the tiny blank row in the diagram. So the drawing problem appears to be specific to key columns.

This message was edited 1 time. Last update was at 2010-03-13 18:39:16

I think you are mixing things here.

The primary key name you enter in the table dialog is the name of the primary key constraint. It does not define a column.

You need to add a column and tick the "In primary key" checkbox to make a column part of the primary key.

Ah, so the real problem is that there's a word ("constraint") missing from the UI.

Thanks for the info.

MobiusStrip wrote:Ah, so the real problem is that there's a word ("constraint") missing from the UI..

No I don't think so.
The input field defines the name of the primary key.

That the primary key is enforeced through a constraint is a technical detail. A DBMS is free on how it enforeces that, it does not need to use a constraint for that.

There is also nothing to inidicate that that single field (without a datatype!) would actually define a column in the table.

castorp wrote:That the primary key is enforeced through a constraint is a technical detail. A DBMS is free on how it enforeces that, it does not need to use a constraint for that.

It would be best to clarify what "primary key" is referring to in the UI. As you point out, we can't assume that this is the name of a constraint.

The lack of datatype may be interpreted as an effort to provide a shortcut that ensures the presence of a primary key, but not a replacement for the column-properties UI.

I haven't encountered this ambiguity with other DB-design tools (Data ERWin, ERStudio, SQL Editor).

Thanks for the info.