field api

A brief summary of the idea:

Data within entities that do not need to be processed individually within a view (or better: are not required to be addressed individually in any case) should be stored in a single database table, rather than being spread over N tables like they would if stored by the Field API "the usual way", in order to reduce the number of (sub)queries or subsequent queries and hereby reduce the load on the site's database.

The "parent term" property on a taxonomy term is a unique, non-field-api, non-transferrable relation that has not been upgraded to Field API. This GSoC idea does not propose to replace this in core as the short term goal, because a transitive relationship field can exist side-by-side with the current "parent term" field and the "parent term" field can be drupal_alter'ed out of existence. However, if this project succeeds, it would be developed further to include in core.

Hej!

Jag ska försöka skapa något som liknar användarprofiler i drupal 7. Via panel och annat ska designen lösas, men jag fattar inte hur jag knyter till användarna de olika fälten. Forut var det profile-modulen som användes. Den ska så vitt jag förstått finnas kvar, men vara avstängd som standard och man rekommenderas använda Fields API istället. Vad innebär detta? Hur ska jag göra?

Lost....

//Markus