Menu

#47 Use terms consistently

open
nobody
None
5
2011-05-27
2011-05-27
No

I find the distinction between fields and items are a major source of confusion when talking about Plomino apps.
For example, when adding a column, there is a control to select the field to be shown for the column.
In reality, this does not necessarily refer to a field on a specific form. It actually refers to (1) an item on a document, or (2) to a field on a random form.

[8:58:41 PM] Jean Jordaan: the reason i got into this is that the column says you should select a field from a form
[8:58:54 PM] Jean Jordaan: but i suspect that isn't actually what happens
[8:59:27 PM] Jean Jordaan: if different forms have the same field there's still only one catalog index
[9:00:01 PM] Jean Jordaan: the value is looked up from the catalog index, so you don't know which field indexed it
[9:00:38 PM] Eric BREHAULT: absolutely
[9:00:46 PM] Jean Jordaan: also if the field with the same name has a different type on different forms, then the type of the index will be the type of the last-saved (or first-created, i'm not sure) field
[9:00:55 PM] Eric BREHAULT: but the fields are listed by form to ease the finding for the user
[9:01:28 PM] Jean Jordaan: hehe that's debatable also ;) it means instead of an alphabetic list of fields, you get the letter R in many disparate sequences
[9:02:34 PM] Jean Jordaan: listing the fields by form implies that e.g. the formula for the computed field on that form will be used, while the document may last have been saved by a different form

Discussion


Log in to post a comment.

MongoDB Logo MongoDB