[buddypress-trac] [BuddyPress Trac] #6350: XProfile field database schema

[buddypress-trac]

#6350: XProfile field database schema
----------------------------------+----------------------------------
 Reporter:  johnjamesjacoby       |       Owner:
     Type:  defect (bug)          |      Status:  new
 Priority:  low                   |   Milestone:  Under Consideration
Component:  Component - XProfile  |     Version:  1.0
 Severity:  minor                 |  Resolution:
 Keywords:  2nd-opinion           |
----------------------------------+----------------------------------

Comment (by DJPaul):

 JJJ, I think this looks OK, but I think it would help illustrate some of
 your bullet points if you could please provide a (sample) MySQL export of
 these tables so the rest of us can compare how the default xprofile
 group/field/data/values would relate to each other, and understand the
 proposed changes better (against our development databases, for example).

 > We could move visibility out of field meta

 I don't see enough benefits to doing this -- unless you can suggest why BP
 would need to be able order fields by visibility when making an SQL query.
 I think the existing JOIN against the meta table for (what is) a key/value
 pair is fine; it only starts to be a hinderance when you try to order
 things by meta value.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6350#comment:5>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac