Re: 115,000 records -- nodes or custom
Earnie Boyd <[email protected]>
| Newsgroups | gmane.comp.php.drupal.devel |
|---|---|
| Message-ID | <CA+sc5mnyCHoFyu3ymTyvqyjeaB1VFEhSgw4unZ99bi267eqLww@mail.gmail.com> |
On Thu, Mar 8, 2012 at 11:22 PM, Cameron Eagans <[email protected]> wrote: > Sigh. Methinks Vaibhav Jain should understand caching a little better before > making statements like that. @op, go with Larry Garfield's advice. It's a > solid plan. But not mentioning it will never give the OP a hint to go learn. The issue is complex with many possible solutions. Depending on how the third party table is being updated it may make sense to give a view to the third party table. If his client wants Drupal to update the third party table then several things could take place. If the table is never to be updated then several other things could take place. -- Earnie -- https://sites.google.com/site/earnieboyd