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
Each date is again a dictionary, containing period_id as keys
Ghost
@ghost~550d34c415522ed4b3dd96cb
If you're willing, you can work with @mafiya69 and make the sql layer use this scheme too.
Sartaj Singh
@leosartaj
Each period_id is a tuple having subject_id and status
@shivamT95 What do you think?
Ghost
@ghost~550d34c415522ed4b3dd96cb
I think it would be better if we did away with the "date" key.
Because, we also have to produce weekly reports, then we would also want to add a "week" key, or derive one when reading data.
Sartaj Singh
@leosartaj
That can be done by reading dates
Now, problem with dates is that they are very restrictive( fixed format)
So, any other suggestion on keys for classes is welcome.
Ghost
@ghost~550d34c415522ed4b3dd96cb
But dates and weeks have a similar feature. They collect data into discrete sets.
If we're not having weeks, we can also avoid having dates.
Sartaj Singh
@leosartaj
We can have weeks.
Ghost
@ghost~550d34c415522ed4b3dd96cb
I'm thinking that we might be able to use both sql and json.
This would make that more convenient.
Sartaj Singh
@leosartaj
That would confuse things.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Otherwise, it's like having a table for every day.
Sartaj Singh
@leosartaj
sql slows things down, as told by @mafiya69.
Also we have some json related functions.
Ghost
@ghost~550d34c415522ed4b3dd96cb
It won't, if we have just one table.
Also, I'm thinking that it would be a install time configurable option.
Completely optional.
Sartaj Singh
@leosartaj
Now, that shouldn't be asked from users.
This will scare people.
Keep it under the hoods.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Many packages do such stuff.
Sartaj Singh
@leosartaj
What I find good with json is, in my credit you can ask for raw data. And i just give you the json.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Ipython notebook only opens when you have 4 other packages installed, which are optional dependencies.
Sartaj Singh
@leosartaj
hmm...Why do you think it will be good, to have json and sql?
Ghost
@ghost~550d34c415522ed4b3dd96cb
A lot of work will go to waste. Also, we might want to shift over to sql if we want more features.
Sartaj Singh
@leosartaj
Yes. That's a nice point.
Ok, what I say is finalise the json.
We then map it into tables.
?
Ghost
@ghost~550d34c415522ed4b3dd96cb
:+1:
Sartaj Singh
@leosartaj
This is confirmed, one table contains all the subject names with a unique id.
Ghost
@ghost~550d34c415522ed4b3dd96cb
We can also go crazy with layers.
{
    "subjects": {
        "name": id
    },
    "classes": {
        "semester": {
            "month": {
                "week": {
                    "date": {
                        "period_id": ("subject_id", "status")
                    }
                }
            }
        }
    }
}
Sartaj Singh
@leosartaj
Oh my.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Semester, month, week & date can be added as columns.
Sartaj Singh
@leosartaj
Better will be sql table I gues. Too much of nesting
Ghost
@ghost~550d34c415522ed4b3dd96cb
Yeah. That's too much nesting.
Sartaj Singh
@leosartaj
So second table is classes.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Yeah.
Sartaj Singh
@leosartaj
Columns - period_id(unique), subject_id, date, status
That will do?
Ghost
@ghost~550d34c415522ed4b3dd96cb
We can use a simple hash for period_id
Sartaj Singh
@leosartaj
And semester to divide things up
Ghost
@ghost~550d34c415522ed4b3dd96cb
A bidirectional hash.
Sartaj Singh
@leosartaj
Man, why not simple 1, 2, 3?
:P