Currently, I have a DB structure in MySQL with dozens of tables with various external relationships between them. All the data is in the files that I upload, so I hope that I can transfer the project to a storage system that works with Drupal 7, because I can just configure something (using the Feeds module?) To get my data as I like Drupal 7. The ultimate goal of this is to do a lot of manual revision of a person, linking table entries with relationships, and possibly processing some field data that doesn't look right. Thus, the whole goal is to make a human interface for viewing and editing relationships (especially adding) in Drupal 7. The question is, what is the correct way to store data, so I need to write as little module code as possible?
It seems to me that I would choose one of 3 modules to perform this task:
- Communication
- Entity reference
- Data
The Relation and Entity Reference will allow me to store all my data in nodes (entities?) In Drupal 7, so Drupal will have “native support” for processing all the material. Nevertheless, I expect that their number will be from 100 million to several billion nodes, possibly up to 3 relationships with other nodes in each. How efficiently does a Relation or Entity Reference link handle this by referencing external data (and possibly capturing the referenced data from this help, etc.) with Views and the like? Can they support a node with a null reference, since many will be null until the user can install them (so I need a way to also have a view for finding nodes with specific null references)?
- , , . , , MySQL, Drupal, Drupal . ?
, , , , Drupal 7 CMS. - , , . (s?) / ( " " ) "" ", , , ? ?