Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>On the data model side that @devnull picked up, you are describing a custom fields implementation and @devnull is describing the <a href="http://en.wikipedia.org/wiki/Entity-attribute-value_model" rel="nofollow noreferrer">EAV</a> model.</p> <p>There's a good stackoverflow article that covers design patterns for custom fields in an application:</p> <p><a href="https://stackoverflow.com/questions/1126783/what-are-design-patterns-to-support-custom-fields-in-an-application">What are design patterns to support custom fields in an application?</a></p> <p>The data model choice and the UI generation are tightly linked, so you can't really answer the UI generation question until you decide on your data model/custom field pattern. My initial reaction was the same as @devnull's on the alter approach, but there really is no great solution.</p> <p>You can reduce a lot of complexity if you have a superset of all possible fields and allow the user to enable/disable the ones that are appropriate to their application domain. I've done several implementations of custom fields in an application with very smart people and it's always hard. If you understand the application domain well enough you can stay away from the uber-flexible architectures and save yourself a lot of grief.</p> <p>Note that an important consideration is whether they will need to query on the custom fields. It's much easier if you don't have to support general querying. You just slot userdate1, usern, etc. and provide a metadata table for labels.</p>
    singulars
    1. This table or related slice is empty.
    1. PODynamic UI Generation in C#
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USRob
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODynamic UI Generation in C#
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COQuerying unfortunately is required for the custom fields. IMO, there will not be much use for the custom field if the user cannot search right?
      singulars
      1. PO
      1. USRanhiru Cooray
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload