Added field to appmetadata table in RFC 3 #6
Loading…
Reference in New Issue
No description provided.
Delete Branch "center/rfcs:tilde-center"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A gross oversight on my part, but the lack of a second foreign key to another appdata entry makes queries between appdata and appmetadata horribly inefficient for its desired use case.
Previously, if a user wanted to make a service like Facebook with one appdata entry (e.g. a user) link to many other appdata entries (e.g. friends) using the appmetadata table, the appmetadata entry would need to convey it was a friend attribute and the ID of the other user in the VARCHAR(32) value field.
Now, for the same appdata-to-appdata relationship, the appmetadata could link to the user, the friend user, and use the value field to denote the relationship of these two entries as “friend”. This new field to appmetadata enabled the power behind using a relational database and can turn what would be multiple SQL queries before into just one.
Is there anything I need to change to have this PR accepted?