CCK and the need for Data Import and Export

Events happening in the community are now at Drupal community events on www.drupal.org.
zoon_unit's picture
Posted by zoon_unit on March 24, 2007 at 11:49pm

I've just finished reading Robert Douglas's excellent article on CCK. And two things struck me when reading about the data structures of CCK:

  • With data that is so highly normalized, how will this impact data access of CCK nodes? Drupal is already very demanding of mysql and I wonder if this will slow down data access even more. Feedback?
  • More and more, Drupal is approaching a web based version of a 4GL, where datesets can be defined and maintained. This makes Drupal more than a CMS; it is now a data access system. But one BIG need remains: a way to get data in and out of those datasets. We desperately need a data import/export system for Drupal that can handle these complex table and field relationships. Has any work been done in this regard?
Categories:

Comments

field data are cached.

Posted by yched on March 25, 2007 at 2:33am
yched's picture

  • field data are cached. When you load a node, the fields values are retrieved from the cache in one query, no JOIN is made on CCK's tables.

  • see 'Import / Export API' module

Is the Import / Export API

Posted by alexmc on April 10, 2007 at 7:56am
alexmc's picture

Is the Import / Export API module really the way to go? I have not really seen much use of it

See alternatives in the CCK

Posted by karens on April 10, 2007 at 11:14am
karens's picture

See alternatives in the CCK Handbook at http://drupal.org/node/89493.

Content Construction Kit (CCK)

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: