Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 07 2020 23:07
    harshita130602 starred numerals/rollcall
  • Jun 07 2018 08:10
  • Jun 21 2015 07:12
    mafiya69 synchronize #17
  • Jun 21 2015 07:12
    mafiya69 synchronize #17
  • May 16 2015 05:48
    mafiya69 synchronize #17
  • May 16 2015 05:21
    mafiya69 synchronize #17
  • May 15 2015 18:22
  • May 15 2015 14:25

    sumitsahrawat on master

    update license Merge pull request #19 from num… (compare)

  • May 15 2015 14:25
    sumitsahrawat closed #19
  • May 15 2015 14:25
    sumitsahrawat commented #19
  • May 15 2015 04:40
    mafiya69 synchronize #17
  • May 15 2015 04:31
    leosartaj commented #19
  • May 15 2015 04:31
    leosartaj opened #19
  • May 15 2015 04:28

    leosartaj on license

    update license (compare)

  • May 15 2015 04:19
    sumitsahrawat commented #18
  • May 15 2015 04:10
    mafiya69 commented #18
  • May 15 2015 03:51
    leosartaj commented #18
  • May 15 2015 03:24
    mafiya69 synchronize #17
  • May 15 2015 02:41
    mafiya69 commented #18
  • May 14 2015 18:33
    leosartaj commented #18
Sartaj Singh
@leosartaj
In sql, I say we keep it simple
Querying will be easy that way
Ghost
@ghost~550d34c415522ed4b3dd96cb
Yeah, well they can be different :smile:
Sartaj Singh
@leosartaj
So, final json or sql?
Json we already have it merged.
Sql, well we will need to.
Ghost
@ghost~550d34c415522ed4b3dd96cb
I'm thinking that this json is good.
Sartaj Singh
@leosartaj
:+1:
period_id be like Date-number
Ghost
@ghost~550d34c415522ed4b3dd96cb
Yeah, that's good too.
It was what I thought initially.
yy_mm_dd_no
Sartaj Singh
@leosartaj
But i still think having a date key will be good.
Sure json looks bad. I think functions will be easy to make
Ghost
@ghost~550d34c415522ed4b3dd96cb
Yeah. I guess you're right.
Sartaj Singh
@leosartaj
{
    "subjects": {
        "name": id
    },
    "classes": {
      "date": {
        "period_id": ("subject_id", "status")
        }
      }
    }
}
Ghost
@ghost~550d34c415522ed4b3dd96cb
I'll take a look at how other projects have done it.
Sartaj Singh
@leosartaj
This will do?
Ghost
@ghost~550d34c415522ed4b3dd96cb
Yeah, looks good to me.
Sartaj Singh
@leosartaj
With this structure. We will be able to make a lot of different queries.
Plus json is suppported by all languages.
Your project can have a similar structure.
Ghost
@ghost~550d34c415522ed4b3dd96cb
The only base requirement I wanted was to be able to blast through all the data at once.
This seems good from that point of view.
Sartaj Singh
@leosartaj
Hmm....Should we also store some generated data, I mean calculated data.
?
Govind Sahai
@0x6773
bakc
Sartaj Singh
@leosartaj
Cool.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Welcome :fire: let's camp.
Sartaj Singh
@leosartaj
@mafiya69 maybe we are going back to json
{
    "subjects": {
        "name": id
    },
    "classes": {
      "date": {
        "period_id": ("subject_id", "status")
        }
      }
    }
}
something like this?
what say?
Govind Sahai
@0x6773
just reading above msgs
Ghost
@ghost~550d34c415522ed4b3dd96cb
I don't think we need to store calculated data.
Sartaj Singh
@leosartaj
You are right. Querying will be trivial anyway.
Ghost
@ghost~550d34c415522ed4b3dd96cb
It'll be better if I can just edit the text file manually and see rollcall understand the changes instantly.
*json file
Sartaj Singh
@leosartaj
You can. :D
Moreover I just worked with this kind of things in credit. I think I can make these changes quickly.
Also, I would like to have something to separate semester.
User doesn't have to delete older data.
I mean reset everything
Semester key?
@mafiya69 What do you think, about json?
Govind Sahai
@0x6773
I think the name of json file will handle that
Ghost
@ghost~550d34c415522ed4b3dd96cb
I'm thinking a separate table that keeps track of semester start and end dates.
Govind Sahai
@0x6773
json?
or sql?
Ghost
@ghost~550d34c415522ed4b3dd96cb
a separate json structure :smile: