Quote:
Originally Posted by kovidgoyal
The restriction on non duplicate column headers is cosmetic only for user convenience. The UI prevents the user from creating duplicate columns because that's typically not a useful thing to do.
|
But earlier you said:
Quote:
Originally Posted by kovidgoyal
You can have any number of columns with the same name. The new builtin column is not visible by default, most people would not even be aware it exists. And since column names is a global namespace such clashes are inevitable, the price of allowing people to create their own columns.
|
That says to me that I should be able to make a *new* cc named 'Pages' (or Title or whatever) if I want, and I can't.
I tested all the standard columns Headings (in English) and got a popup "ERROR: The heading X is already in use" for each --
except Authors, 'On device' and Size.
Quote:
Originally Posted by kovidgoyal
But you can actually have as many duplicate header names as you like (lookup names have to be unique). Thus there is no issue with having a builtin column with title Pages and a custom column with title Pages as well.
|
If you mean it's not harmful to the library and won't break anything when importing a library that already has a Pages header cc, I'm not disputing that.
I'm not saying that the dup Header check should be removed; but what I see happen appears to contradict your earlier post, and is inconsistently applied (Author etc).