John M Camara, el 28 de enero a las 19:40 me escribiste:
> Leandro has posted a link to his code which I just took a look at.  It 
> appears to be written in Spanish which makes it a little challenging 
> for myself to completely comprehend it as I only know English.  It 
> does appear that for his application that a relational database would 
> be fine.  I would like to understand why he had issues with both SO 
> and SA but it would take me far too long to translate all the names in 
> his code to English so I can make better sense of the code.

Yes, I'm sorry about posting it in spanish, but as I said I'm a little
short o f time right now to clean things up. But I can offer you a simple
translation here in a form of a "dictionary". The system is for
educational pruporses, it handles courses, teachers, students and
exercises:
Curso = Course
Usuario = User
Docente = Teacher
Alumno = Student
Tarea = Work (not from the student, it's a work done on the exercise by
              the system, like compile it or run testcases to it)
Enunciado = Exercise (like an entity by itself)
CasoDePrueba = Testcase
Ejericio = Exercise (the association between Enunciado and Course)
InstanciaDeEntrega = Timespan on wich the student can delive an exercise
DocenteInscripto = association between Docente and Course
Entregador = Something that can deliver an exercise
Grupo = Group (of Alumnos in a Curso, students can make some exercises
               individually and other groupally_
AlumnoInscripto = association between Alumno and Course
Tutor = association between DocenteInscripto and a Group, a group can have
        some teacher assigned to it to guide the students.
Miemrbo = association between AlumnoInscripto and Group (membership)
Entrega = deliver (created when a student/group deliver an exercise)
Correccion = correction (a selected Entrega to be corrected by a
             DocenteInscripto)
TareaEjecutada = association between Work and Entrega, it's the results of
                a particular work execution on a delivered exercise
Prueba = one kind of special Work is to run testcases, for each testcase
         runned a Prueba is created with the results of the run.
        
The rest are identity classes and attributes, which I don't think they are
that relevant. My main problem was on with the associations between
inherited objects, like Grupo, DocenteInscripto, AlumnoInscripto, Miembro,
Tutor, etc.

(excuse me about the bad english/translation, there are a lot of terms
that I don't know exactly how to translate but I hope it gets a little
clearer)

The main goal on this system is not statics or reports, even when some
could be appreciated, it's not that ugly to construct them in a OO way
because they will be mostly limited to a particular Course, so the data to
analyze is not too largea and a query language is not estrictely neccesary.
So maybe this is a case where OODB could be a good choice.

-- 
Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/
 .------------------------------------------------------------------------,
  \  GPG: 5F5A8D05 // F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05 /
   '--------------------------------------------------------------------'
Parece McGuevara's o CheDonald's

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to