How Glittery will evolve its comments mechanism!

Just in case you missed the previous post about the architectural changes we’ll be making to GlitterGallery, you can find that here.

Since Glimages will now be shown through the blob object’s data, there’s actually an advantage  – we can now support comments for every point in history for a particular Glimage. The URL for a particular commit will contain the sha for the commit. (An SHA is unique to a commit).

Screenshot from 2013-09-02 17:42:02So, all we have to do now, is grab that SHA, and assign that to a comment. Just like we relied on the glimage_id column earlier, we’ll now rely on the commit’s SHA for the same!

Of course, we’ll want to assign these comments to Glitterposts as well, so’ll actually be dealing with two columns. type and type_id. It probably makes sense to prettify things a bit, so we’ll organize our tables in this fashion (comment_holder connects those two tables):

Screenshot from 2013-09-02 18:13:24This looks error free to me so far, although if you have any feedback, you must let me know! 🙂


One thought on “How Glittery will evolve its comments mechanism!

  1. Pingback: Glittery’s changes in the file storage schemes – some more desi cola

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s