Changes between Version 70 and Version 71 of VersionOneFeatures


Ignore:
Timestamp:
06/01/2007 10:12:35 AM (8 years ago)
Author:
bouldersprinters
Comment:

More details about Oracle status for Django 1.0

Legend:

Unmodified
Added
Removed
Modified
  • VersionOneFeatures

    v70 v71  
    1111|| generic relations               || Jacob/Malcolm  || Yes             ||  Code move is done (Malcolm), admin support (Jacob) not done. Needs newforms-admin merge first.  ||    ||
    1212|| [#Comments comments]            || Jacob       || Yes           || in progress                       || #1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189   ||
    13 || [#Oracle oracle]                || ?           || No           || almost there                      ||    ||
     13|| [#Oracle oracle]                || ?           || No           || done                      || #4140, #4186   ||
    1414|| ms sql server                   || ?           || No           || ?                                 ||    ||
    1515|| test fixtures                   || Russ        || No           || done                              || #2333 ||
     
    5252=== Oracle ===
    5353
    54 While it doesn't change APIs, having an oracle backend is great
     54While it doesn't change APIs, having an Oracle backend is great
    5555for the 1.0 release, even if it doesn't contribute to the #1 goal. And
    56 there is great impetus behind it.
     56there is great impetus behind it.  Please see the [wiki:OracleBranch Oracle Branch] wiki page for technical details.
     57
     58#4140 needs a design decision: should we warn or disallow database reserved words when used as column names?
     59
     60#4186 is a significant limitation of Oracle and CLOB columns that can't be worked around, so we've at least documented the limitation clearly.
    5761
    5862=== Root View and URL Reversal ===
Back to Top