HUE-2166 [core] Oracle database support in doc model
Review Request #4450 — Created June 13, 2014 and submitted
Information | |
---|---|
abec | |
old-hue-rw | |
HUE-2166 | |
Reviewers | |
hue | |
enricoberti, romain |
commit 42f9917b512413addb9855cd882d5b1506bb6e44 Author: Abraham Elmahrek <abraham@elmahrek.com> Date: Fri Jun 13 14:40:39 2014 -0700 HUE-2166 [core] Oracle database support in doc model :100644 100644 cce8416... 130d91b... M desktop/core/src/desktop/migrations/0007_auto__add_documentpermission__add_documenttag__add_document.py :000000 100644 0000000... bf4aac2... A desktop/core/src/desktop/migrations/0008_documentpermission_m2m_tables.py :000000 100644 0000000... befa81e... A desktop/core/src/desktop/migrations/0009_auto__chg_field_document_name.py :100644 100644 eafd0d9... 4695e19... M desktop/core/src/desktop/models.py
Migrations work for the following cases: - Brand new install. - Existing installation. Data may go missing unfortunately... Thought of introspecting for database names and columns names for oracle only? Seems a bit overkill. Users should probably just perform a "dumpdata" and reload the data. This does not fix the "ORA-00932: inconsistent datatypes: expected - got NCLOB" errors.
-
Looks good! So basically we create the tables with a shorter name. Existing 5.0 installation that upgrade are going to work because 0008 also add them in case. Two last comments: #1 Normally the only drawback is that all the perms of C5.0 are lost. There is no way to rename the table instead in 0008_documentpermission_m2m_tables.py? #2 Is install examples working correctly?