<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi,</div><div><br></div><div>I think there is a compatibility issue. In this case, it's because sqlparse added a bunch of "new" keywords (from oracle) that conflict with identifiers we already use. We got as far as trying to retroactively rewrite all our *past* schema updates to be compatible (by quoting table / column names) but iirc that brings us out of sync with all existing CalendarServer DBs. Fixing that correctly would be a significant undertaking, requiring a schema update to rename everything. I think there may be a more hacky option of customizing the sqlparse keyword list at runtime to remove the conflicting keywords, but we didn't do that. I think there may have also been a problem around not easily being able to make that customization early enough and at the right layer.</div><div><br></div><div>Related: <a href="https://lists.macosforge.org/pipermail/calendarserver-dev/2016-November/001799.html">https://lists.macosforge.org/pipermail/calendarserver-dev/2016-November/001799.html</a><br><br><div>-dre</div></div><div><br>On Dec 18, 2016, at 6:50 AM, <a href="mailto:amaramrahul@users.sourceforge.net">amaramrahul@users.sourceforge.net</a> wrote:<br><br></div><blockquote type="cite"><div><div style="font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; line-height:1.3; color:#000000"><div style="font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; line-height:1.3; color:#000000"><div><div id="composer" style="font-family:Calibri, Arial, Helvetica, sans-serif;font-size:12.0pt; line-height:1.3; color:#000000" class="airwise-not-deletable airwise-keep-content-inside composer_editor"><div style="font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; line-height:1.3; color:#000000"><div>This is regarding <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848361">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848361</a><br><br>I need to look into this but before I begin to debug the issue, I just wanted to do a quick check to see if there are any known compatibility issues of calendarserver 7.x with sqlparse 0.2.2? If so, is there a patch / commit id that I can backport?<br></div><div><br></div><div id="signature-x" style="-webkit-user-select:none; font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; color:#000000" class="signature_editor">Sent from <a href="http://www.9folders.com/" style="text-decoration:none;color:#009BDF">Nine</a><br></div></div></div></div></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>calendarserver-dev mailing list</span><br><span><a href="mailto:calendarserver-dev@lists.macosforge.org">calendarserver-dev@lists.macosforge.org</a></span><br><span><a href="https://lists.macosforge.org/mailman/listinfo/calendarserver-dev">https://lists.macosforge.org/mailman/listinfo/calendarserver-dev</a></span><br></div></blockquote></body></html>