[Building Sakai] 2.9.0 DB Conversion, MySQL script error

[Sam Ottenhoff]

On Thu, Jan 24, 2013 at 7:47 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> So how is a new developer meant to know all of these unwritten rules if
> they aren't described anywhere?
>

As a community, we've decided to support MySQL and Oracle.  I don't like
fixing Oracle syntax issues especially because I don't run Oracle.  But I
help fix them because I want institutions that run Oracle to use Sakai.  If
Oracle changes syntax that breaks Sakai queries, we'll fix Sakai.  It's yet
another thing that we developers need to learn and adapt to.  If you use
opposite cases with MySQL, someone will eventually catch it and correct it.
 Here are the rules of our dependency, MySQL:
http://dev.mysql.com/doc/refman/5.1/en/identifier-case-sensitivity.html



> I disagree that there are too many requirements.
>


I can't imagine you are in the majority.


My point is that if the rule you proposed was enforced on table creation,
> not just updates, you wouldn't have that mess.
>
>
The rule I proposed was consistency, that's all. I'm too busy right now to
make consistent all table names in Sakai CLE. Until the day I have the
time, or someone else volunteers, I will continue to fix JIRAs like the one
originally reported in this thread.

--Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130124/af1cf2af/attachment.html