Response Time
24 — 48 hours
I'm a little concerned about the database layout for the photo meta data located in _social_photos_meta. For two photos it stores quite a few records as seen here:
Eventually if I have a million photos posted, 16 million records would need to be created for those photos.
I'm concerned that the number of records might slow down the system when the database is called upon.
Joomla stores a set of data in a single record for users in the following format (in the table _users):
{"admin_style":"","admin_language":"","language":"","editor":"codemirror","helpsite":"","timezone":"America\/Los_Angeles"}
In fact, they not only have the set but other data in a single record as seen here:
I'm not sure which way is the right way, but I'm raising this as a concern to make sure the best practices are being used. Would a dataset slow it down vs the current method being used?
Eventually if I have a million photos posted, 16 million records would need to be created for those photos.
I'm concerned that the number of records might slow down the system when the database is called upon.Joomla stores a set of data in a single record for users in the following format (in the table _users):
{"admin_style":"","admin_language":"","language":"","editor":"codemirror","helpsite":"","timezone":"America\/Los_Angeles"}
In fact, they not only have the set but other data in a single record as seen here:
I'm not sure which way is the right way, but I'm raising this as a concern to make sure the best practices are being used. Would a dataset slow it down vs the current method being used?
7 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
