[Building Sakai] [Using Sakai] Gradebook database relations

[Gregory Guthrie]

Thanks.
Yes, I understand the points about database vs. API, but for a new user and someone who wants to "use" Sakai instead of becoming a Sakai developer, the cost/benefit difference is significant.

I can figure out & setup the database queries in a day or so, but learning and setting up a development environment, and learning the internal models, API, and usage of Sakai would take much longer.

So this is at least something to get us going!

Thanks, 
Greg

-------------------------------------------
> -----Original Message-----
> From: Mark J. Norton [mailto:markjnorton at earthlink.net]
> Sent: Monday, September 03, 2012 7:51 AM
> To: Gregory Guthrie
> Cc: sakai-user at collab.sakaiproject.org; sakai-dev at collab.sakaiproject.org
> Subject: Re: [Using Sakai] Gradebook database relations
> 
> There isn't much more to the code than the algorithm I providing in my previous message.
> The actual code is proprietary.  Probably the hardest part is getting the GradebookService,
> which lives in the edu-services component.
> 
> Coding directly to the Sakai database tables is strongly discouraged.
> The whole point of creating a service with a published API is to avoid access to the
> underlying storage mechanism, which may change at any point in the future.  For example,
> grading information (in theory) could be stored in a Jackrabbit database, which is not
> relational.  Likely this doesn't matter since you are developing an application for your
> university rather than targeting many.
> 
> - Mark Norton
>