2 Replies - 686 Views - Last Post: 03 July 2012 - 10:51 AM Rate Topic: -----

#1 atraub  Icon User is offline

  • Pythoneer
  • member icon

Reputation: 759
  • View blog
  • Posts: 2,010
  • Joined: 23-December 08

NOSQL - how would you handle this?

Posted 03 July 2012 - 08:34 AM

Hey guys,

Right now I'm learning about NOSQL for work, and I'm thinking about how it would relate to an earlier project I've worked on. Imagine there was a database holding student records. Some of these students were also tutors, and this database also has a table that holds tutoring session records. So the tables might look something like this

Student Table
  • id
  • name


Subject Table
  • subject name


tutoring session
  • tutorer's ID
  • learner's ID
  • subject



I'm trying to get my mind into a NOSQL mentality. I know this is NOT the way you'd do something like this in a nosql environment, but how would you mimic it? The benefit is that using the session table, you can get all the tutoring or learning records of a given student from their ID. To do something like this in NOSQL, would you have to put the data for a given tutoring session onto two student entries?

This post has been edited by atraub: 03 July 2012 - 08:35 AM


Is This A Good Question/Topic? 0
  • +

Replies To: NOSQL - how would you handle this?

#2 atraub  Icon User is offline

  • Pythoneer
  • member icon

Reputation: 759
  • View blog
  • Posts: 2,010
  • Joined: 23-December 08

Re: NOSQL - how would you handle this?

Posted 03 July 2012 - 08:46 AM

Ahh, changed my search terms a little and found this. It seems that the answer they've come to is, don't use NoSQL :P
Was This Post Helpful? 1
  • +
  • -

#3 JackOfAllTrades  Icon User is offline

  • Saucy!
  • member icon

Reputation: 6078
  • View blog
  • Posts: 23,546
  • Joined: 23-August 08

Re: NOSQL - how would you handle this?

Posted 03 July 2012 - 10:51 AM

Yeah, NoSQL is NoGOOD for relational data :)
Was This Post Helpful? 2
  • +
  • -

Page 1 of 1