Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

mysql: optimize the tagMap mechanism #109

Closed
llorllale opened this issue Apr 29, 2021 · 2 comments
Closed

mysql: optimize the tagMap mechanism #109

llorllale opened this issue Apr 29, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@llorllale
Copy link

The tagMap mechanism of the mysql storage implementation should be optimized. It is being stored as a composite value of a single record in the data table. Instead, the tags should be maintained in a separate 'tags' table. Queries, updates, and deletions involving the tagMap should not require SELECT prior to UPDATE/DELETE. Furthermore, it should be possible to do bulk updates/deletions to the tag map (see Batch()).

@llorllale llorllale added the bug Something isn't working label Apr 29, 2021
@DRK3
Copy link
Contributor

DRK3 commented Apr 29, 2021

@llorllale Note this issue here: #88

Really the entire "tag map" mechanism should be replaced with columns + SQL indices. The "tag map" was just a "quick and dirty" solution to allow it to function per the interface requirements.

@llorllale
Copy link
Author

OK - closed as this is a duplicate of #88

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants