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
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
Ghost
@ghost~550d34c415522ed4b3dd96cb
No date, we calculate the period_id in such a way that it determines the date too.
Sartaj Singh
@leosartaj
If we are into sql. Why not keep it simple?
Ghost
@ghost~550d34c415522ed4b3dd96cb
Well, the date would be repeated many times.
Sartaj Singh
@leosartaj
Yeah. But it's sql.
It's common.
Ghost
@ghost~550d34c415522ed4b3dd96cb
Also, that simplifies the json to this:
{
    "subjects": {
        "name": id
    },
    "classes": {
        "period_id": ("subject_id", "status")
    }
}
Sartaj Singh
@leosartaj
That will be good for json your idea.
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.