CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Database schema modifications in 2.0
Pages: [1]

Author Topic: Database schema modifications in 2.0  (Read 1495 times)

tdilliga

  • Guest
Database schema modifications in 2.0
November 14, 2007, 02:23:01 pm
I'm wondering if changes to the database schema will be made to eliminate the civicrm_location.entity_table / civicrm_location.entity_id (and similar in other tables). This seems to:

1) Introduces a huge performance hit when you have a large number of people registered for an event.
2) Prevents relational key checking.

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Database schema modifications in 2.0
November 14, 2007, 05:24:06 pm

yes, we've eliminated quite a few of the entity_id/entity_table things. You can check more details here: http://wiki.civicrm.org/confluence/display/CRM/CiviCRM+v2.0

feedback would be great and much appreciated

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions (Moderator: Dave Greenberg) »
  • Database schema modifications in 2.0

This forum was archived on 2017-11-26.